Firstly: what are you trying to achieve
Firstly: what are you trying to achieve? (it will count against your compute time - it’s not a way to get free compute!)
3 Replies
I'm simply creating a workflow to perform some tasks, but I would want a portion of those tasks to be async. Thats when I realized I wasn't really sure what would happen if I used
waitUntil.
My main questions are:
1. Does the waitUntil'd process extend the life of the step or the overall workflow worker itself?
2. Does a step failure/retry have any effect on the waitUntil'd process?
@Matt just checking in if there's any update here1. It extends the workflow, which means any results can get swallowed.
2. No.
I don’t think you should use it - it makes sense for a HTTP request where you don’t want to block a response, but in a workflow - which is already async - you don’t need it.
Thanks! I figured as much, but since the feature is technically available in Workflows and I didn't see anything in the docs about it I wanted to be sure.