Flow Not Triggered by Catalog Item

[ericgilmore]

Looks like something went wrong on my Dev instance. It's not triggering flows associated with catalog items. It's still working in my Test and Prod instances. I'm not seeing anything in the logs that looks suspect or in the active contexts. Nothing looks as though it changed with business rules, script includes, etc.

When I click the flow context related link on the request item, I get this:

Is there somewhere else I should look for possible hitches to the process?

[Rajesh Chopade]

Hi,

The message you received - 'Waiting for flow execution data' simply means that for some reason the execution data isn't available yet. There must have been an issue during the processing of the flow where it wasn't able to complete and/or return the execution data.

Although since re-saving has worked - it could be a one off glitch. 

I've experienced something similar in flow designer where the save hangs and I need to refresh / re-save.

Regards

[ericgilmore · Accepted solution]

Well, it looks like something changed. The flow started and pushed through the activities I expected. I'm not sure if another admin did something or if some other process woke up, but looking at the logs about 12:05p (pacific) an upgrade check started.

Upgrade check: instance already running assigned version: glide-orlando-12-11-2019__patch9b-02-04-2021_02-05-2021_2157.zip

Then nothing until about 12:40p when I'm seeing a multitude of entries with TableCleaner as the source. Somewhere in there the flows/workflows woke up.

So, some sort of update stop all processes issue, or maybe the update coincidentally occurred during this problem? I dunno. But things seem to be working now.