---
sourceDocument: Australia Build workflows
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/build-workflows

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# Subflow history

# Subflow history {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 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 Subflow History

The Subflow History feature allows users to view and manage the history of a subflow, including configurations and changes made over time.
This functionality is crucial for tracking modifications, restoring previous versions, and managing subflow configurations effectively.
Show full answer Show less  

## Key Features

* **Flow History View:** Provides detailed entries with timestamps, the user who made updates, and operation types.
* **Actions:** Users can annotate entries, mark favorites, filter entries by type or user, copy, restore, or delete history entries.
* **Flow History Entry Types:** Includes force saved, deactivated, activated/published, autosaved, restored, and deployed entries.
* **Filter Options:** Easily filter entries to manage visibility and organization.
* **Automatic Save Overwrite Interval:** Controls how autosave entries are managed to avoid excessive history records.
* **Favorite Flow History Entries:** Up to 20 favorites can be marked to prevent overwriting during entry limits.
* **Flow History Entry Limit:** Default storage is 100 records, with options to adjust this limit through system properties.

## Key Outcomes

By utilizing the Subflow History, ServiceNow customers can efficiently manage subflow configurations, ensuring that important versions are preserved and easily retrievable. Users can annotate entries for clarity, restore previous configurations as needed, and maintain an organized record of changes, which enhances operational efficiency and collaboration among team members.  
View and manage the history of a subflow. See past configurations of a subflow to copy, restore, or remove them.  
The flow history view enables you to perform these actions.

* View the configuration for each flow history entry.
* See the date and time stamp of when a flow history entry was created.
* See the user name of the person who updated the subflow.
* See the type of operation that created the flow history entry.
* Add an annotation for a flow history entry.
* Add a flow history entry as a favorite.
* Filter flow history entries by type or user.
* Save a copy of a flow history entry as a new subflow.
* Restore a flow history entry as the current configuration of a subflow.
* Delete a flow history entry.
{#subflow-history__ul_yvx_z1c_hdc}

## Flow history components {#subflow-history__section_kyk_ds5_3fc}

Figure 1. Flow history components of a subflow  
The Flow history view consists of these components within a subflow.

1. Flow History view
:   Label indicating that you are looking at a particular flow history entry. There's also an option to return back to the subflow editing view.

2. Name of the flow history entry
:   Name of the flow history entry as a unique date and time stamp.

3. Flow history options
:   Options to delete, save as copy, and restore a flow history entry.

4. Flow history list
:   List of flow history entries. Each entry has a card listing subflow details and options.

5. Flow history card
:   Card listing the subflow details of the flow history entry. Details include the date and time stamp when the subflow was created, any annotation describing the subflow, the user who made the flow history entry, and the type of
    subflow operation that created the flow history entry. Each card also provides options to add the history entry as a favorite, add an annotation, or delete the flow history entry.

6. Flow sidebar views
:   Views available to display in the sidebar. The sidebar can display the subflow data or the subflow history. There's also an option to display the help panel.

## Flow history entry types {#subflow-history__section_cz4_mxw_jfc}

The system creates flow history entries whenever someone perform one of these operations.  
{#subflow-history__table_wzh_hyw_jfc__entry__2}

| Operation | Description |
|-|-|
| Force saved | Entry created when someone uses the Force save option to manually save the subflow configuration. For more information about force saving a subflow, see [Save as you go flows](https://servicenow-prod.fluidtopics.net/A27mjcn8uv9Bd8ICeMPptw "Save flows, subflows, and actions automatically as you work on them."). |
| Deactivated | Entry created when someone deactivates an active or published subflow. |
| Activated/Published | Entry created when someone activates or publishes a subflow. |
| Autosaved | Entry created when someone performs an operation that autosaves the subflow. For more information about what operations automatically save a subflow, see [Save as you go flows](https://servicenow-prod.fluidtopics.net/A27mjcn8uv9Bd8ICeMPptw "Save flows, subflows, and actions automatically as you work on them."). |
| Restored | Entry created when someone restores a subflow to a prior configuration. |
| Deployed | Entry created when someone creates a new subflow or deploys the subflow on this instance from the application repository or an update set. |
[Table 1. Flow history entry types]

{#subflow-history__table_wzh_hyw_jfc}

## Filter options {#subflow-history__section_q4h_fxw_jfc}

You can filter flow history entries by type or user.  
Figure 2. Flow history filter options

Select a history entry type to show it in the flow history list. Clear a history entry type to hide from the flow history list.

You can filter flow history entries to show flow history entries from all users or just your flow history entries.

## Automatic save overwrite interval {#subflow-history__section_b2t_bfc_4fc}

By default, Workflow Studio overwrites autosave history entries that are made by the same user during a 60 minute interval. All autosave history entries generated by the same user during this interval are saved as one history entry.
During this interval, the most recent autosave history entry overwrites the previous autosave history entry. The save interval reduces the number of flow history entries generated by one user, which helps prevent reaching the history
entry limit. You can set the automatic save overwrite interval using the sn_flow_designer.autosave_version_interval system property. For more information about this system property, see [Workflow Studio flow system properties](https://servicenow-prod.fluidtopics.net/QISjE_DknwhS_u_mrxbXbQ "Configure how the system processes flows.").

## Favorite flow history entries {#subflow-history__section_x43_jnc_4fc}

Each subflow can have up to 20 favorite flow history entries. Marking a flow history entry as a favorite prevents the entry from being overwritten when the flow history entry limit is reached. You can also use favorites to communicate
to other users that the entry contains a valuable configuration that should be saved. When a subflow reaches its history favorite limit, you must remove an existing favorite before you can add a new one.

## Flow history entry limit {#subflow-history__section_lrv_zfv_3fc}

By default, Workflow Studio stores 100 flow history records. When the total number of flow history entries exceeds this limit, Workflow Studio overwrites the oldest history entry that is not marked as a favorite. You can set the maximum number of flow history records to store using the sn_flow_designer.maximum_flow_history_records_per_flow
system property. For more information about using this property, see [Workflow Studio flow system properties](https://servicenow-prod.fluidtopics.net/QISjE_DknwhS_u_mrxbXbQ "Configure how the system processes flows.").
* **[View subflow history](https://servicenow-prod.fluidtopics.net/25gFbgfrda15gD_jixoVCA)**   
  View the change history of a subflow by date and user.
* **[Add an annotation to a subflow history entry](https://servicenow-prod.fluidtopics.net/ZzQnepbU3_jPJd7aAe6a1A)**   
  Add a text description to a subflow's flow history entry. Summarize the purpose or contents of a particular flow history entry.
* **[Delete a subflow's flow history entry](https://servicenow-prod.fluidtopics.net/djhbjcZ9nhSueTMbAeMWMA)**   
  Delete a subflow's flow history entry from the flow history list.
* **[Restore a subflow to a previous flow history entry](https://servicenow-prod.fluidtopics.net/SA5LcEDAi_VnXVbwmGCsAw)**   
  Restore a subflow to a previous configuration. Create a new flow history entry for the restore operation.
* **[Save a copy of a subflow's flow history entry](https://servicenow-prod.fluidtopics.net/GzhJqUjJ6fwC3_Ywp3jGrw)**   
  Create a copy of a flow history entry and save it as a new subflow.