I’m experiencing an issue with a delay in the execution of a Data Cloud–Triggered Flow.
I created and activated a Data Cloud–triggered flow on 17/12/2025, but it only started firing on 23/12/2025, even though a full data refresh from Snowflake to Salesforce Data Cloud is performed daily. The flow is configured to execute on record creation/update of a custom Data Model Object (DMO) and update the corresponding Account record in the Salesforce home org.
The flow worked correctly on 23/12/2025 and 24/12/2025. However, on the evening of 24/12/2025, I made an update to the flow, saved it as a new version, and activated that version. Since then, the flow has not fired again.
Is this kind of delay common for Data Cloud–triggered flows?
Do I need to wait
5–6 days every time I update and activate a new version of the flow?For reference, a full data refresh from Snowflake to Salesforce Data Cloud runs daily. Full refresh deletes all data from data cloud and then creates new data and after each refresh all records are created again in data cloud so it should invoke flow for record creation and before update it was invoking the flow.
Hi Shafaqat,
What's the condition for triggering the flow? System will look for changes post the flow activation date only.
If the refresh of data didn't create a matching triggering criteria the flow won't be triggered.
Is the triggering flow checks the change in data? When full refresh is done brand new data comes in. It won't be changed as well.
Thanks
