Pruning executions in 'waiting' stage?

Questions
1

Hi guys!
Quick questions. I have a workflow running where clients receive a custom scripted email for 52 weeks in a row. All 1 week apart from each other.

I’m on the starter plan (cloud) and I only see executions that started a week ago, which kind of worries me.

I was under the assumption that workflow executions would not be pruned as long as their status was still ‘waiting’. But now I don’t see them in the executions logs any longer.

So the question is:

Are those executions still active, but I simply cannot view them any longer?

Or have they been terminated due to the pruning?

2

Did you create the workflow so it waits everytime and keeps waiting untill the next email?

If so I suggest storing them for later sending instead of having ur executions be waiting all the time.

They are probably cleaned up as it is probably assumed those are stuck executions. Or because of some limits on cloud with regards to runtime/wait time.

3

Not sure what you mean by ‘storing them for later sending’?

And yes, the workflow is created in a way that it waits everytime for 7 days until the next email.

5

Send the needed data to a datatable for example (built in feature) and then have a scheduled flow check when next email should be send and send it then.

6

hope you’re doing well @NLSolutions
They should still be active, waiting executions are not pruned, so if they no longer appear in your logs, I think it is more likely a Cloud retention/visibility limit than the executions being terminated.