[TRI-321] Better handle errors bubbling up in subtasks

[ericallam]

Currently when viewing a failed task because a subtasks threw an error is not a great experience. We need to improve that

When a subtask fails (and all retries are done) the error doesn't bubble up to the parent task. Instead you get a very generic: "Error: Task errored at IO.runTask".

Instead, a failed subtask should bubble that error up to parent tasks (so the subtask error is duplicated onto the parent).

You can easily reproduce this by creating a task with subtask inside that throws a specific error.

_{From SyncLinear.com | TRI-321}

[ericallam]

/bounty $50

[algora-pbc]

💎 $50 bounty created by ericallam
🙋 If you'd like to work on this issue, comment below to get assigned
👉 To claim this bounty, submit a pull request that includes the text /claim #159 somewhere in its body
📝 Before proceeding, please make sure you can receive payouts in your country
💵 Payment arrives in your account 2-5 days after the bounty is rewarded
💯 You keep 100% of the bounty award
🙏 Thank you for contributing to triggerdotdev/trigger.dev!

[SSHari]

@ericallam would it be possible to get more information about what the bad experience is and what the expected experience should be?

[tonie-ng]

/attempt #159

[rishi-raj-jain]

@matt-aitken @ericallam

Would it be possible to get more information about what the bad experience is and what the expected experience should be?

[matt-aitken]

I've added more information to the original issue

[matt-aitken]

@RamK777-stack would you like to claim the Algora bounty?

[RamK777-stack]

Yes @matt-aitken

[RamK777-stack]

claim #159

[algora-pbc]

💡 @RamK777-stack submitted a pull request that claims the bounty. You can visit your org dashboard to reward.

[algora-pbc]

🎉🎈 @RamK777-stack has been awarded $50! 🎈🎊

[matt-aitken]

This was fixed