> ## Documentation Index
> Fetch the complete documentation index at: https://university.triggr-app.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Cache
> Keep a workflow's result ready, refreshed hourly, daily, weekly or monthly, so form dropdowns load instantly and workflows can reuse it.
Data > Cache keeps a workflow's result and refreshes it on a schedule, so a form dropdown that needs a slow lookup, such as your PSA's ticket categories, loads instantly. Workflows can read it too. You need the [Admin role](/studio/clients/team-and-permissions#roles).
## Example: ticket categories for a form
Build a workflow whose last data step produces the list, such as `{ "id": …, "name": … }` items from your PSA, ending at a Finish Workflow step. On that step's Settings tab, enter a variable name, tick **Publish Variable** and save (see [Save an output under a short name](/studio/workflows/expressions#save-an-output-under-a-short-name)).
Click **New Cache Definition**, name it, set Scope to Global, choose the workflow, enter the variable's name as the Published Variable Name, pick a Frequency and click Create Cache Definition.
Scope starts on Per Tenant, which keeps one value per client ([Per-client caches](#per-client-caches)); Global keeps one for everyone. Leave Workflow Params as `{}`.
Open the definition, click **Run on Demand** and confirm; otherwise it first fills at its next scheduled time.
Refresh the page: Current Cache Value shows when it was filled, and Execution Logs lists each run.
View Cache Data shows what's stored:
In the form designer, click a Select field, set **Options Source** to Use cache and choose the cache definition. Value Key and Label Key start as `id` and `name`; change them if your items use other fields.
The dropdown now lists the cached items:
## Read it in a workflow
Add **Get Cache Data** from Cache, choose the cache definition and leave Tenant ID empty for a global cache. The stored value is in `value`: `{{ ctx.steps['Get Categories'].value }}`.
| Step | What it does |
| - | - |
| Get Cache Data | Returns the stored value, or runs the workflow and waits if there isn't one yet |
| Refresh Cache Data | Runs the workflow now, waits and stores the new value |
| Invalidate Cache Data | Deletes the stored value; the next read or scheduled run fills it again |
When a workflow adds a ticket category in your PSA, for example, end it with Refresh Cache Data so the form shows it straight away.
## How it refreshes
* The frequency counts from when you created the definition: a Daily cache created at 09:10 UTC refreshes at about 09:10 UTC each day.
* A stored value stays until a run replaces it; if a run fails, forms and workflows keep the last good value and Execution Logs shows why.
* Each run has 5 minutes, and a value can be up to 10 MB.
* Invalidate Cache deletes the stored values; Edit changes the definition or disables it, and changing its workflow, published variable or scope also clears the values.
## Per-client caches
With Scope set to Per Tenant, Triggr stores a value per client, or for the clients you pick. Each run gets the client's ID in `ctx.metadata.tenantId`, so start the workflow with a Set Client From Form step to load that client's variables and integrations. A form reads the signed-in person's client's value; in Get Cache Data, set Tenant ID to `{{ ctx.client.id }}`.
## Troubleshooting
Check the step's Settings tab has Publish Variable ticked, the name matches the definition, and the run reaches Finish Workflow.
Fetch less, or split the workflow into several caches.
The cached value must be a list of items that each have the Value Key and Label Key fields; check its shape with View Cache Data.
The Get Cache Data step for a Per Tenant cache needs Tenant ID set to `{{ ctx.client.id }}`.
On the definition's page, click **Edit**, set it to Enabled and save.
An internal app can't. An AI assistant connected through [MCP](/studio/mcp) can, with Cache tools such as `get_cache_entries` and `run_cache`.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.