. However, I know that for certain kinds of errors, I’d actually want it to wait 30 minutes (or even an hour). Is there a way to implement this? I know I can probably just check for that exception then
time.sleep
for the extra time (for example, to wait for an hour I’d catch the exception,
time.sleep
for 45 minutes, then raise the error so that
retry_delay
kicks in), but I’m wondering if there’s a cleaner way to approach this.
The above feels like a code smell but I’m not sure how I’d otherwise set context-specific retry delays on a task 🤔
a
Anna Geller
12/22/2021, 9:39 PM
You’re 100% correct that there is no straightforward way to configure it atm. Another user asked about a variable number of retries and here is a hacky solution I came up with.
It will be easier in Orion, but for now you need a workaround e.g. using the KV Store.
k
Kevin Kho
12/23/2021, 4:17 AM
I think this can be done inside the state handler. If you have an error, you can access it with
Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.