Screencast:
https://www.loom.com/share/b4f94aadc2984345b093478f73dd6f03
I've tried to retrigger some recently failed tasks from a scheduled task, but nothing happens.
#Retrigger tasks from ui not working
polar acorn
Hmm it triggered now, but the ui is not reflecting the run
teal hedge
Can you share a link to the page above?
polar acorn
I had to clear the filter
teal hedge
That's ok, it's still there under "Filter" -> "Bulk action"
We persist all bulk actions so you can go back and check whether the replayed runs succeeded
polar acorn
Hmm maybe it's just very delayed, eg I cancelled some tasks here:
https://cloud.trigger.dev/orgs/doldadress-f80c/projects/v3/api-uVcB/runs?bulkId=bulk_5mcxbnpmb1znro9wuoeao
But it does not show the tasks...
The same thing happened here after the bulk retrigger:
https://cloud.trigger.dev/orgs/doldadress-f80c/projects/v3/api-uVcB/runs?bulkId=bulk_47tbuff41bcswm619rww9
However now it shows the tasks
teal hedge
Only runs that were "cancellable" will appear in that list for the first one. That means they were either pending or executing. If they were already in some kind of final state (success, failed, system failure, crashed, cancelled) then they wouldn't appear. Maybe it was that? Sometimes you bulk-select but by the time you've clicked they're finished.
We're hopefully going to make this page live soon… it's super annoying needing to manually refresh it.
polar acorn
I guess it's just the queue, but as +5 minutes passed I thought the tasks where not being re-triggered
Sounds good!
teal hedge
The other thing that might have happend here is that when you click "Replay" it adds them to a list to be triggered, then processes them. This is async so it can take a little bit of time if there are a lot or the queue is large.
It shouldn't take more than 5 seconds normally to trigger them though. There was a higher volume of these than normal today and we've actually increase the supported volume for this operation. So hopefully it'll be faster to bulk replay in future 🙂