During metadata deployment (for example, via VS Code or Metadata API) involving a Platform Event–Triggered Flow, event processing behavior is temporarily impacted if the deployment includes changes to that flow.
This behavior ensures controlled activation of flow changes and maintains system stability during deployments. Although no platform events are lost, a short delay in processing may occur depending on the deployment duration and complexity.
This article explains why platform events published during a Platform Event–Triggered Flow deployment may be processed with a short delay, and how to reduce that impact. This is expected behavior.
Platform events published during a Platform Event–Triggered Flow deployment may experience a temporary delay in processing. Once deployment is complete and the flow is activated, all relevant events will be processed as expected — no events are lost.
005321537

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.