function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
Larry WasserLarry Wasser 

Flow Never Continues: Expected FLOW_WAIT_WAITING_DETAIL Never Receives a Transaction Id (of form "OFo19....)

After repeatedly running an Autolaunched Flow, the Flow reaches exactly the same Pause node (after several prior EVENT/PAUSE/RESUME sequences) and never executes anything further.

Launch Autolaunch Flow (CORE Automation - CAU Routing) via Debug interface.
Flow proceeds through all prior sequences of:
- Create Platform Event (consumed by Process Builder, which publishes response Platform Event)
- Wait for response Platform Event
- Resume Flow Execution

Reaches next Create Platform Event, which receives an EventId
Continues to the next Flow node which is a Pause node
Pause node NEVER receives an Id (0Fo19.....) associated with the FLOW_WAIT_WAITING_DETAIL as all prior Pause nodes had received.

This is issue is reproducible with identical behavior.

No Errors are found in the logs
No Errors are Posted to Chatter
No Errors are sent via Email
Flow remains Paused in the Paused Flow Interviews, but is paused at the Pause element immediately prior to the Pause element at which the issue occurs.

Image of color-coded Flow Transaction Log FilesScreenshot of Flow Builder
AbhishekAbhishek (Salesforce Developers) 
Hi Larry,

The below articles might help you,

https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_debugging_system_log_console.htm

https://help.salesforce.com/articleView?id=process_troubleshoot_debuglogs.htm&type=5

This also might be related to it,

https://success.salesforce.com/answers

I hope you find the above solution helpful. If it does, please mark as Best Answer to help others too.


Thanks.
 
Larry WasserLarry Wasser
Hello Abishek, Unfortunately the answers link wasn’t pointing to a specific answer. Please resend. Thanks, Larry
Larry WasserLarry Wasser
Just a follow-up to all. Met with a Salesforce Regional Architect. No system error could be found. Was advised to transition to development in Apex.