How to know when a workflow ends?

[akieffer]

I was wondering if, by any mean, it was possible to know when a scheduled workflow ends.

I’m running a “schedule workflow on a list” task and I’d like to trigger an event when the last workflow on this list has terminated.
I tried something with the workflow IDs:
1st- adding them in a list
2nd- remove each workflow ID just before the end of the workflow
3rd- trigger an event when the list is empty
The problem is that when an error occurs, the ID is not removed.

Anyway, this solution seems really overkill and I’m pretty sure there’s something I’ve been missing.

[reger-alexander]

Instead of scheduling a workflow on a list, I would recommend to run the workflows recursively.

[New Feature] Scheduling API workflows can now be done recursively

Hi all, We had previously restricted scheduled API workflows from scheduling themselves (or scheduling another workflow that then scheduled itself). This restriction is now removed. Recursive scheduled workflows can be useful in situations where you are processing an unknown quantity of data that might be quite large. For instance, the following workflow will make sure every Thing in your database has been processed within 7 days: [39%20PM] [45%20PM] Processing data this way is generally …

You can count your list items on initialization and hand over a counter number recursively. When the counter = list item count, it is the last item.

[akieffer]

Wow, didn’t even know you could run workflows recursively!
Thank you for the tip, this will definitely do the job