It would be great to have an Auto Replay or Rerun option per recipe. We have a lot of "Request timeout" errors that could be replayed a couple of minutes later.
This feature is available in Zapier:
Please this is badly needed.
I am busy with "Request timeout" every 15 minutes
+1 on the update. I've been dealing with timeouts on SQL Server. A workaround that I found is that you can use error monitoring and a callable recipe to rerun the job. Example if the job fails you pass the data back to another callable recipe that will process it again. It's basically a one time rerun but it cut my errors down by 90% because it usually runs successfully on the second try.
Auto replay would be great to have indeed!
We don't have this on the roadmap yet but I'll definitely point this out to the product team and keep you posted if we have any updates. Thank you.
Being able to rerun the job in the error actions would be ideal. It could be based on an If criteria like error = time out. Quickbooks API is having intermittent issues which means that if Quickbooks jobs fail the have to be manually rerun each time it fails.
To be able to rerun failed jobs in the following 2 new manners would be GREATLY appreciated (by everyone it seems) :-)
2) Recipe triggered rerun (so we can rerun failed jobs by using other recipes): think for instance a recipe that when fails sends a Slack message to the admin with a "Rerun failed job now!" action button. Clicking that button would send the failed job id to a callable recipe that reruns it on demand. No more need to go to Workato every single time, locating the failed job in the log and rerun it :-)
Hope you guys manage to get this into the roadmap somehow. At least please add a new method to Workato's API to rerun failed jobs by ID and we'll use REST to do the rest (no pun intended).
please please add this in, even if its just for errors like timeouts
You can now do this using Error with Monitoring Action.
When there is an error in any of the monitored actions, the actions described in this block will be processed.
If retry count is set, the monitored actions will be processed again. After all the retry attempts result in errors, the actions in the error block will be processed.
Retries can be conditional. Only when specified condition is true, actions in the monitored block will be retried. Otherwise error actions will be processed.
Great job on this. I think this design is very very good and it's very helpful.
Seconded, great addition, was very much needed :)
Send us a ticket, we will try our best to assist you with your problem