The Workflow Context (WFC) is the current state and the resources and data available during a workflow's execution.
Core concept
Every time a workflow runs, it gets its own Workflow Context. When a job creates, manipulates, or loads metadata or resources, it does so only in the current WFC, isolated from other, concurrent runs of the same workflow.
Anything stored in the WFC is only available for that execution. Once the run finishes, the WFC and everything in it is gone, unless the data was also stored more permanently, for example on a unit, in a data log item, or in the file library.
Resources in the WFC
Resources are the objects a workflow works with. They can be permanent (stored on your account, such as units or groups) or temporary (existing only in the WFC for the duration of the run).
Common temporary resources include:
- The incoming message or HTTP request that triggered the run
- A temporary group of units used for in-run processing
- Data created by a job to be used later in the same run, such as a CSV resource
See Working with variables for the syntax used to read and write resource and metadata values in the WFC.
Metadata: temporary vs. permanent
Metadata can be stored temporarily in the WFC or more permanently on a resource such as a unit. Use the WFC for values only needed during the current run, and save to a permanent resource when the value needs to outlive the execution.