Overview
Run attributes are key/value facts about how a Run went. Your automation sets them while it runs, the caller can pass initial ones when it starts the Run, and you can replace them after the Run ends. Intuned stores them with the Run and each Attempt and returns them wherever you read Run results. Use attributes for small, structured facts that describe the Run rather than its output:- Where the data came from —
source: "cache"orsource: "live" - How the Run went —
pagesScraped: 12,aiFallback: true,stage: "checkout" - Who or what started it —
trigger: "scheduled",batch: "2026-10-25"
Set attributes from your automation
CallsetAttribute (TypeScript) or set_attribute (Python) anywhere in your API code. Setting a key again overwrites it. deleteAttribute / delete_attribute removes a key.
Values and limits
setAttribute / set_attribute throws an error when a key, a value, or a limit is invalid, so a mistake shows up while you develop instead of being dropped silently.
Pass initial attributes when starting a Run
The caller can start a Run with initial attributes. Every Attempt starts with them, and your code can overwrite or delete them.- Standalone Run
- Job payload
Add
attributes to the body of the Run start request:400.
Update attributes after a Run ends
Once a Run has finished (succeeded, failed, or canceled), you can replace its attributes, for example to mark it as reviewed or to add a fact only known later.- API
- CLI
- Dashboard
Send the complete new map to the attributes endpoint:The response holds the stored attributes:
- The map replaces the old one. Keys you leave out are removed, and
{}removes them all. To change one key, read the Run’s attributes first, change it, and send the whole map back. - Finished Runs only. A Run that is still pending or running returns a
409. While a Run executes, your code owns its attributes. - Attempts don’t change. Each Attempt keeps the attributes it reported.
- Same limits. The values and limits apply, and a request that breaks them returns a
400. - Already delivered results don’t change. Sink payloads and job result files keep the attributes they were delivered with.
How attributes work across Attempts
- Each Attempt starts fresh. It starts with a copy of the initial attributes, not with what a previous Attempt set. A retry doesn’t see the failed Attempt’s changes.
- Each Attempt keeps its own. You can see what every Attempt set on its Attempt details.
- The Run starts with its final Attempt’s attributes. Attributes are not merged across Attempts. After the Run ends, you can replace them.
- Deleted means gone. If your code deletes every attribute, including the initial ones, the Run reports none.
- Canceled before it ran. A Run that is canceled before any Attempt reports keeps its initial attributes.
- AuthSession Runs. Validate and create Runs report the attributes of the Attempt their result comes from: the passing check, or the successful create when the AuthSession was recreated.
Where attributes show up
Run metadata
Next toattributes, the same places return metadata: facts about the Run that Intuned sets from its own records. Your code can’t set or change it.
metadata. Sinks return it as apiInfo.metadata, and the Job result file has it on each line as apiInfo.metadata.
Limitations
- Not for customer data. Attributes are stored inline as operational metadata. Keep personal and regulated data in your API’s result.
- Small values only. The limits above are enforced when your code sets an attribute. Use the API result for anything larger.
- No merging across Attempts. The Run starts with only its final Attempt’s attributes.
- Requires a recent Runtime SDK.
setAttributeandset_attributeare available in the latest@intuned/runtimeandintuned-runtime.
Related resources
setAttribute (TypeScript)
Runtime SDK reference
set_attribute (Python)
Runtime SDK reference
Runs (single executions)
Start Runs and get their results
Jobs (batched executions)
Batch and scheduled Runs