--- sourceDocument: Brazil Build workflows sourceDocumentLink: https://www.servicenow.com/docs/r/build-workflows Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil Build workflows ft:clusterId : - crworkflow bundleId : - crworkflow workflow : - Creator --- # Flow execution details retention # Flow execution details retention {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Flow execution details retention ServiceNow instances manage the large volume of data generated by flow execution details through data retention policies that automatically delete records after specific time periods. This ensures optimal system performance and storage management. Flow execution details are primarily generated during test runs or when flow reporting is activated. Show full answer Show less ## Flow Execution Data Management The system stores different types of flow execution content in dedicated tables, each with its own default retention period and cleanup rules. Records older than these periods are deleted if the flow is in a completed state. The retention periods vary depending on the flow state (completed, error, or canceled), typically ranging from 2 to 6 weeks. ## Key Tables and Retention Periods * **sysflowcontext:** Stores all flow context records and associated process plans. Retention is 2 weeks for completed flows and 6 weeks for error or canceled flows. Excessive retention here can degrade instance and flow performance. * **sysflowcontextchunk:** Holds runtime data for active flows; data here should not be modified or deleted manually. * **sysflowcontextchunkarchive:** Contains data for inactive flows, with the same retention as sysflowcontext. * **sysflowreportdoc and related chunk tables:** Store execution detail reporting data for active and inactive flows, following similar retention rules as context tables. * **sysflowlog:** Contains replicated log entries to correlate logs with flow contexts; retained for 28 days or until table rotation. * **sysflowplancontextbinding:** Maintains unique identifiers for flow triggers to enforce "run once" or "for each unique change" conditions, retained for 12 months. Removal of these records may cause reruns of flows under certain conditions. ## Practical Considerations * Disabling or extending retention periods, especially for **sysflowcontext**, can negatively impact system and flow performance. * Manual changes or deletions in active state tables (**sysflowcontextchunk** , **sysflowreportdocchunk**) are strongly discouraged to avoid flow errors. * If flow execution details are purged due to retention policies, the flow report will display messages indicating unavailable action reports and disabled action details. ## Recovery Options If flow data is removed and needed for analysis, customers can contact ServiceNow Customer Service and Support to request data restoration from instance backups. Recovery requests are subject to backup availability and retention policies documented in the Now Support Knowledge Base. Due to the large amount of data consumed by flow execution details, your instance uses data retention policies to delete this data after a set time period. ## Generating flow execution details {#flow-reporting__section_xr5_k1v_gbc} By default, the system only generates execution details when you run a test. To generate flow execution details, see [Activate flow reporting](https://www.servicenow.com/docs/~ilzGOS6xzr_ee06F~0Ibw#enable-flow-reporting "Choose whether to generate execution details for all flows and actions run, just for individual flows and actions, or just when you test a flow or action. Specify the level of detail the execution details contain.") ## Scheduled table cleanup {#flow-reporting__section_zgy_gsh_z2b} The system uses a standard table cleaner records to determine when to remove execution details. Each type of flow execution content is stored in its own table and has its own retention period. Once a record is older than its default retention period, it is deleted if it is in a completed state. To learn more about how to find and configure table cleaner records, see [Table cleaner](https://www.servicenow.com/docs/access?context=table-cleaner&version=brazil&pubname=brazil-platform-administration&ft:locale=en-US). {#flow-reporting__table_hmm_shn_z2b__entry__3} | Table | Description | Default retention period | |-|-|-| | sys_flow_context | Parent table that stores all Workflow Studio context records and their associated process plans. Context records store the state and references to the data used to run a flow or action. See the child tables for context records in specific states. Warning: This table doesn't support running custom business rules. Trying to gather state information from this table may cause performance issues or unexpected flow errors. | * 2 weeks for completed flows * 6 weeks for flows in the error or cancelled state {#flow-reporting__ul_aln_kcs_nrb} Warning: Deactivating or increasing the retention period of Flow Context records can negatively impact instance performance. Retaining more flow contexts can impact flow performance and the ability to use new flow features. | | sys_flow_context_chunk | Child table that stores context records and runtime data for currently running flows and actions. This table replaces the sys_json_chunk table as the location to store data for active context records. A running flow or action can be in one of these states. * Continue Sync * In Progress * Queued * Waiting {#flow-reporting__ul_bfx_pqg_jtb} Danger: Do not change or delete data in this table. Workflow Studio uses this table for flows and actions that are in an active state. | The system removes these records when the flow stops running and creates an entry in the sys_flow_context_chunk_archive table. | | sys_flow_context_chunk_archive | Child table that stores context records and runtime data for flows and actions that have stopped running. This table replaces the sys_json_chunk table as the location to store data for inactive context records. A stopped flow or action can be in one of these states. * Cancelled * Complete * Error {#flow-reporting__ul_mwt_hvm_jtb} Note: Workflow Studio uses this table for flows and actions that are in an inactive state. | Removed when the associated sys_flow_context record is removed. * 2 weeks for completed flows * 6 weeks for flows in the error or cancelled state {#flow-reporting__ul_o51_fbj_ktb} | | sys_flow_report_doc | Parent table that stores references to Workflow Studio context records that have execution detail reporting data available. See the child tables for the execution details of flows and actions in specific states. | The system removes these records when it removes the parent context record from sys_flow_context. | | sys_flow_report_doc_chunk | Child table that stores the reporting data and execution details for currently running flows and actions. A running flow or action can be in one of these states. * Continue Sync * In Progress * Queued * Waiting {#flow-reporting__ul_vtm_tpg_jtb} Danger: Do not change or delete data in this table. Workflow Studio uses this table for flows and actions that are in an active state. | The system removes these records when the flow stops running and creates an entry in the sys_flow_report_doc_chunk_archive table. | | sys_flow_report_doc_chunk_archive | Child table that stores the reporting data and execution details for flows and actions that have stopped running. A stopped flow or action can be in one of these states. * Cancelled * Complete * Error {#flow-reporting__ul_jtl_jqg_jtb} Note: This table replaces the sys_json_chunk table as the location to store reporting data for inactive execution details. | The system removes these records when it removes the parent context record from sys_flow_context_chunk_archive. * 2 weeks for completed flows * 6 weeks for flows in the error or cancelled state {#flow-reporting__ul_ec3_5cj_ktb} | | sys_json_chunk | Table that stores compiled process plans for future, running, and completed flows and actions created prior to the San Diego release. Danger: Do not change or delete data in this table. Workflow Studio uses this table for flows and actions that are in an active state. | The system removed these records when it removed the parent record. | | sys_flow_log | Table that stores replicated log entries from the Log \[syslog\] table. Enables users to correlate logs with flow contexts. | The system removes these records in 28 days when the table is rotated or when it removes the context record, whichever comes first. The table rotation on sys_flow_log is configurable. For more information, see [Table rotation](https://www.servicenow.com/docs/access?context=c_TableRotation&version=brazil&pubname=brazil-platform-administration&ft:locale=en-US). | | sys_flow_plan_context_binding | Table that stores a unique identifier for each context record and the trigger that started it. Whenever a triggering event occurs, the system calculates the unique identifier and compares it to a sys_flow_plan_context_binding record. If the calculated unique identifier matches an existing sys_flow_plan_context_binding record, then the triggered flow is not started. Note: This unique identifier is used to determine when to run flows with either the "run once" or "for each unique change" conditions. | The system removes these records 12 months after creation. Important: The system may rerun flows whose unique identifier was removed by the retention policy. For example, if the trigger conditions of a "run once" flow are met, and the sys_flow_plan_context_binding record was removed, then a new unique identifier is created and the flow runs. | [Table 1. Flow reporting data tables] {#flow-reporting__table_hmm_shn_z2b} ## Unavailable flow data {#flow-reporting__section_x5w_zz2_bfb} A message displays at the top of the flow report to indicate that action reports are not available for a flow because of table cleanup. The Show Action Details link and Action states are not available in this case. A similar message is shown to indicate when reporting for a flow has been deactivated. In this case, a link to the report settings also displays.Figure 1. Sample flow execution details with data removed by the report retention policy ## Recovery options {#flow-reporting__section_kdf_1d3_45b} [Contact Customer Service and Support](http://www.servicenow.com/support/contact-support.html) to restore data from an instance backup. To know the period until which a data recovery request is accepted, see the [Instance Backup and Recovery \[KB0547654\]](https://support.servicenow.com/kb_view.do?sysparm_article=KB0547654) article in the Now Support Knowledge Base.