Step-Level Executions

Statuses & charges

• Charge for this attempt: Shows exact Step credits and Glow AI tokens with the read/write split (e.g. 0 Step credits · 319 Glow AI tokens (257 read · 62 written)).
• Funding badge: Included allowance runs show Glow-funded: not charged and Funded by Glow with a link to Billing details.

Retries & loop entries

A single run can record multiple entries for one Step:

• Loops and junctions: Run for each item writes one entry per item, and Repeater writes one per pass. An OR junction runs for each arrival, while AND waits for all inputs.
• Retry chains: Entries show markers like Attempt 2 of 3 (where the total reflects the highest attempt recorded so far). Group entries by Execution ID and timestamp. See Retry on fail.

30-day retention

Runs are kept for 30 days after completion by default (“New runs are kept for 30 days. Each run keeps the policy in effect when it started.”). This window covers both the workspace Execution log and Step-level input/output payloads.

To retain data longer, write records to an external store during the run (e.g. via HTTP Request) or contact your account team about workspace retention options. See System Limits.

Tracing inputs & wrappers

Downstream references match the recorded output shape. Native app actions expose fields directly ({{ 4.id }}), whereas HTTP Request wraps responses under ret ({{ 3.ret.id }}):

To inspect what a Step received as input, match the Execution ID on each referenced upstream Step and check any inline pipe transformations. Use Custom Variables to log assembled values directly.

Live data mapping

When a Step runs, Glow caches its output to populate the Workflow data picker in downstream Steps with real sample values.

Handling errors

Failed attempts appear in red and display the integration or engine Error Message:

{ "message": "Request failed with status code 404 (Not Found) - {}" }

Compare the error against the Step’s fields and upstream outputs from the same Execution ID. Before repeating a send, create, update, or charge action, check the connected app to confirm the write did not already take effect. See Connections and External APIs and Troubleshooting & Common Errors.