Nesting background action jobs?
I have a bunch of background jobs setup in Trigger.dev (before Gadget offered them) that I'd like to bring across into Gadget so everything is in one place.
However, they currently make heavy use of Trigger's nested "tasks", which allow you to break a big background "job" up into smaller units, each of which can have their own retry logic, and allows a run to be resumed from a particular task - skipping the previous successfully completed tasks within a run.
See: https://v2docs.trigger.dev/documentation/concepts/tasks for full details.
With the new background actions, is a pattern like this possible to replicate? I was thinking that perhaps enqueuing child actions as "tasks" from within a parent enqueued action "job" might work? Is that supported?
Curious to see how others have approached this, particularly around a large background action failing halfway through and what happens when it retries.
However, they currently make heavy use of Trigger's nested "tasks", which allow you to break a big background "job" up into smaller units, each of which can have their own retry logic, and allows a run to be resumed from a particular task - skipping the previous successfully completed tasks within a run.
See: https://v2docs.trigger.dev/documentation/concepts/tasks for full details.
With the new background actions, is a pattern like this possible to replicate? I was thinking that perhaps enqueuing child actions as "tasks" from within a parent enqueued action "job" might work? Is that supported?
Curious to see how others have approached this, particularly around a large background action failing halfway through and what happens when it retries.
