Summary
To improve system stability and performance, Execution Data History files will be limited to a maximum size of 30 MB.
If an execution history file exceeds this limit and the selected log level is greater than BASE, the platform will attempt to regenerate the execution history at the BASE log level. This reduces the amount of recorded detail and helps keep the file within the maximum size limit.
Effective Date
Monday, September 28, 2026
Details
As Architect flows have become increasingly complex, execution history file sizes have grown significantly. While the vast majority of execution history files are smaller than 2 MB, some have grown to nearly 500 MB. These unusually large files can slow processing, place unnecessary load on the services responsible for collecting execution history, and impact overall platform stability.
Introducing a maximum file size helps maintain consistent performance and improves service reliability.
Customer Impact
No impact is expected for the vast majority of customers.
For the small number of customers whose execution history exceeds 30 MB:
- Execution history will be recorded at the BASE log level instead of the selected log level.
- Execution history will continue to include:
- The actions that were executed.
- A summary of each action's behavior.
- Detailed diagnostic information, such as input and output values for actions, may be omitted. These detailed values are typically the primary contributor to very large execution history files, particularly in complex flows with numerous actions and loops.
Impacted Resources
No API is impacted.
Issue References
[CW-4939]
Contacts
@Charles Cafrelli Please reply to this announcement with any questions. This helps the wider developer community benefit from the discussion. We encourage you to use this thread before contacting the designated person directly. Thank you for your understanding.