Hi i am facing an issue about reoccurring scheduled workflow. Yesterday, I ran a single scheduled recurring backend workflow, and it consumed more than 749k WU. kindly guide me on how to optimize workload units?
here’s screenshots:
What do your server logs show?
It looks like you’re probably just running the workflow continuously for 24 hours straight…
Thank you Adam. Its just showing that the workflow started running, Action condition failed and started running again.
yeah i am running this workflow for 24 hours until it meets the condition.
@adamhholmes is there anyway to debug the backend workflow. so i will know exactly the error?
For 24 hours, running every millisecond? (or however long it takes to re-schedule the action… probably more like every second or so)?..
That’s 80-odd thousand runs… No wonder it’s costing so much.
1 Like
Yeah but i need to it every second until the order related changes is yes or if after 24 hours no change occurred then it will previous steps will happened.
sorry for my ignorance, can you tell me that what will be my condition?
Well if you need it to run every second, then that’s fine… but if it costs 10 WU each run, and it runs for 24 hours then that’s approx 800k WU, so if you’re ok with that then there’s no issue.
But why do you need to run it every second?
Why do you even need a recursive workflow here at all? What are you trying to do?..
1 Like
okay so the scenario is that we are having two users one customer and one seller so whenever customer book an order and seller deliver it(some documents) then the customer should have to confirm it. if the customer didn’t confirm it within 24 hours then it should be marked as order didn’t delivered properly.
When the order is created, schedule a backend API workflow to run in 24 hours. Inside this workflow, make changes to the order only when the delivery hasn’t happened.
1 Like
system
Closed
9
This topic was automatically closed after 70 days. New replies are no longer allowed.
Forum
Academy
Marketplace
Showcase
Pricing
Features
