I am using flow to send SMS to a customer. This works fine, but for new Messaging End Users, it can take up to 10 minutes before the SMS is sent and the Messaging Session is created.
I need to link the messaging session to the case where the users started the flow from, but the session isn't available right away.
I tried to use a record triggered flow on Messaging Session, but the flow isn't triggered. Any ideas to why the new Messaging Session doesn't trigger the flow?
This is a known challenging behavior with Messaging Sessions, especially for first-time inbound/outbound setup where Salesforce handles the creation asynchronously behind the scenes. Sometimes, system-created records or automated process users don't trigger standard record-triggered flows as expected, or the delay happens because of the queue processing for new End Users.
Here are a few things you might want to check or try:
1.Run in Asynchronous Path: If you haven't already, try moving your logic to an Asynchronous Path in the Record-Triggered Flow on Messaging Session to see if it catches the late-created record.
2.Trigger from the Case/Process side: Since the user is starting the flow from a Case, can you capture the initial SMS trigger event instead? If you are using an Omnichannel flow or a specific Action to send the SMS, you might be able to pass the Case ID directly into the routing context.
3.Use Platform Events: If the standard trigger fails due to the 10-minute system delay, using a Platform Event to handle the linkage asynchronously could be a more reliable workaround.
Hope this gives you some directions to test!
