Scheduled workflow is exhausting entire app usage bandwidth (498k work units)

Hi everyone,

I have currently implemented a simple backend scheduled workflow, which either creates a new thing or modifies an existing thing based on a condition, and then recalls the scheduled workflow with an increased counter.

When this workflow is running it manages to exhaust all my working units.

Please see below the setup of the workflow.

Would really appreciate any help in debugging the workflow and the usage it is experiencing.

show screen shot of each action in detail so somebody could tell you what is wrong with it.

It looks (on first appearance) like you have a recursive workflow that schedules itself on a list (so it scales exponentially).

This topic was automatically closed after 70 days. New replies are no longer allowed.