> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/developers/workflow-progress.md). # Read workflow progress and outcomes Read a run using the same API key that started it. ```http GET /api/v1/triggers/runs/RUN_ID?account_id=WORKSPACE_ID Authorization: Bearer YOUR_DISTRO_API_TOKEN ``` Required scope: `visual_workflows:start`. Another key cannot read the run simply because it belongs to the same member. ## Response The response includes `run_id`, `workflow_id`, `status`, `finished_at` and `outcome`. The completion time can be null while work is still in progress. Interpret the actual outcome before advancing your application. A redirect outcome contains `type: "redirect"` and `url`. A scheduler outcome can include `scheduler_id`, `event_type_id`, `expires_at`, `token`, availability/booking URLs and a page URL. A closed scheduler has a different outcome shape. Do not interpret a scheduler outcome as a completed booking. Scheduling can leave a run waiting for the guest. ## Custom scheduling limitation The workflow outcome's token authorizes scheduling mutations. Receipt and attempt-status reads use a separate receipt credential that this API response does not expose. As a result, these endpoints do not yet provide a complete custom workflow-scheduling client contract on their own. Do not build a polling client that reuses the mutation token for receipt reads, or assume the bare page URL is sufficient authorization. Use the supported [Form SDK](/forms/sdk.md) for a visitor workflow scheduling journey. For server-side booking through an existing personal/group link, use the separate [Scheduling-link API](/developers/scheduling-links.md). The run endpoint is a progress/outcome endpoint; do not assume it returns an arbitrary JSON object from every internal workflow step. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.distro.so/developers/workflow-progress.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.