--- title: "Outcome Caching" slug: "outcome-caching" description: "Configure Outcome Caching to store Step outputs temporarily, improve performance, and quickly access data from resource-intensive or high-volume Flows." tags: ["Outcomes", "cache", "caching", "cache definition"] updated: 2026-09-29T20:21:13Z published: 2026-09-29T20:21:13Z canonical: "documentation.decisions.com/outcome-caching" --- > ## Documentation Index > Fetch the complete documentation index at: https://documentation.decisions.com/llms.txt > Use this file to discover all available pages before exploring further. # Outcome Caching ## Overview In contrast to [Bespoke Caching](/version-10/docs/cache-steps) via **Flow** steps, **Outcome** **Caching** allows users to store information on the **Output**/**Outcome** of a step. Rather than creating a copy for long-term use, Outcome Caches can be configured to hold onto stored data for a set amount of time. Outcome Caching is particularly useful for users who may need to quickly fetch or make copies of Flow Data easily accessible, such as for a [Table Integration](/version-10/docs/alternate-access-pattern-table-integrations) or when [authenticating a Token](/version-10/docs/creating-oauth-tokens). Because the cached output is tied to a specific Step (and this could be a Sub Flow), it is extremely useful for Steps that are resource intensive and are part of Flows that have high volumes of traffic. ### Outcome Caching Limitations Due to the nature of caching the **Outcome** of a step, information that is cached from steps cannot be fetched via a **Get From Cache** step. As a result, this cached data cannot be used outside of the Flow for further evaluation or retrieval purposes, and can only exist for the set **Cache** **Timespan**. To access data outside of the origin Flow, users may need to create a [Cache Definition](https://documentation.decisions.com/version-10/docs/cache-definitions) and adjust its [configuration](https://documentation.decisions.com/version-10/docs/changing-cache-configuration-settings). The user may also need to write to a [Time Cache Definition](/version-10/docs/writing-to-a-time-cache-definition) to access the data. Also note that each unique step in a flow has its own cache key, even if it is the same kind of step or subflow. --- ## Example The following example demonstrates how to **cache** the **Outcome** of a **Fetch** **Entities** step. 1. From a Designer Project, [create a new **Flow**](/version-10/docs/create-flows). 2. From the Flow Designer, add and configure a [Fetch Entities](/version-10/docs/retrieving-entities-with-the-fetch-entities-flow-step) step to use the Account data type. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1779211701613.png) 3. Still in the **Properties** tab, navigate and expand the OUTCOMES category. Then, select the desired setting from the **Cache** **Outcomes** dropdown (for this example, **PerUser**).  | Outcome Type | Description | | --- | --- | | None | No Outcome data is cached | | Global | Caches all outcome data for all Accounts in the environment per | | Per User | Only caches outcome data for the user that executes the step | ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1779211749221.png) 4. Set a **Cache** **Timespan** by inputting the values into each box, or adjusting the value via the slider. This will determine how long the **Outcome** data remains within the **Cache**. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1779212546820.png) 5. In **v10.3+**, steps that utilize Outcome Caching will display a badge with a tooltip that says: "Step Outcomes Are Cached". ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2026-09-29_15h54_17.png) 6. **Save** the Flow. 7. To confirm this from the **Flow** **Designer**, select the **Debug** link from the top **Action** **Bar**. Click START DEBUGGING. After the **Flow** runs, select **Fetch Entities > Execution 1 > View Output Data**. The Output Data will remain cached for five minutes. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1779211806432.png) --- ## Custom Cache Key RecommendationsThis feature is not recommended for use. It may be deprecated in future versions. Rather than use the unique key that is generated by Decisions, a user can set a custom key. Setting a Cache Key will cause a Step to return the initial cached outcome for the duration of the set timespan. The Step will ignore its inputs on future Flow runs. In this example, a Flow adds two numbers (5000 and 1000) together to get a total of 6000. That total is given a Custom Key, and the Output is 6000. When the Flow is run again, the values have changed; the same Custom Key is used, but the Output remains 6000. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1779212255699.png) To configure, follow steps 1-3 above, select the Custom Cache Key option, and set the Cache Key. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1779212298823.png) --- ## Feature Changes | Description | Release Date | Version | Developer Tag | | --- | --- | --- | --- | | To improve visibility, cached steps now display a cache badge with the tooltip "Step Outcomes Are Cached", making them immediately identifiable on both the Debugger and the Flow Designer. | October 2026 | 10.3 | DT-041967 |