Grid82
grid82.comJoin the waitlist
WorkflowsRetry a run

Retry a run

Only a run that failed or was stopped.

POST/v1/apps/{appId}/workflow-runs/{runId}/retry

It restarts at the step that did not finish: every step before it keeps its saved result and does not run again. from names that step; null means the run restarted from the beginning, where the steps before it run again, except record writes, which return the record they wrote the first time. Use it after fixing the data or the roles, not for a code error (save and activate a new version).

Requires the scopes workflows:write, records:read, records:write, schema:read. Operation workflows.runs.retry. MCP tool workflows_runs_retry. CLI: grid82 workflows runs retry (npx grid82).

Path parameters

NameTypeRequiredDescription
appIdstringyes
runIdstringyes

Headers

NameTypeRequiredDescription
Idempotency-KeystringnoAny unique string. Sending the same key with the same request again returns the first response (marked Idempotency-Replayed: true) instead of running it twice. Reusing it for a different request is refused with 409. Kept for 24 hours. Up to 255 characters.

Response

application/json

Success

dataobjectrequired

Use these docs with your AI tools

An AI agent can read this documentation directly. You do not need an account or an API key. Everything here is public and read-only.

Query these docs via MCP

Recommended

Add this server to Claude, Claude Code, Cursor, Mistral, or any tool that supports MCP. Your agent can then search Grid82 documentation and read it in full, instead of answering from memory.

https://grid82.com/docs/mcp
  • searchFind the passages that answer a question.
  • fetchRead one page in full, as Markdown.
  • list_pagesSee every page in this documentation.

Query these docs over HTTP

The same tools also work as plain web requests. Use this for scripts, or for any tool that does not support MCP. There is one endpoint per tool. Arguments go in the query string, and the answer comes back as JSON.

https://grid82.com/docs/api/docs/search?query=custom+domain

Read the OpenAPI description. It is built from the same definitions as the tools, so it always matches what the endpoints do.

Read these docs as Markdown

Add .md to any page URL to get its Markdown source. You can also send the headerAccept: text/markdown to the page URL itself.

To read the whole documentation in one file, open llms-full.txt. For a short index of every page, open llms.txt.