> ## Documentation Index
> Fetch the complete documentation index at: https://docs.plungeai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# plungeai_get_workflow_status

> Check the status of one of your executions (self-heals stuck runs). Returns structured content too, including `continuation` when the run is paused awaiting user approval or an answer — relay that to the user and use plungeai_continue.


Check the status of one of your executions (it self-heals stuck runs). It also returns structured content, including `continuation` when the run is paused awaiting the user's approval or answer: relay that to the user and use `plungeai_continue`.

**Returns.** A Markdown status block and `structuredContent` with `execution_id`, `status` (`running`, `completed`, `incomplete`, `failed`, `cancelled`; `incomplete` only for async runs, since a sync call stamps its run `ok`, which then reads `completed`), `error_message`, `workflow_name`, `started_at`, `duration_ms`, `final_task_id` and `continuation` (`{status, agent, question, pending_action}` or null). A `running` row with a stored result is healed to `completed`; one with no heartbeat for more than 960 seconds is marked `failed` (`Interrupted (run did not complete)`; the reason shows from the next read on). Details: [9.3](https://mcp.plungeai.com/docs#93-check-status-plungeai_get_workflow_status).

```bash
curl -s https://mcp.plungeai.com/v1 \
  -H "Authorization: Bearer $PLUNGE_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"plungeai_get_workflow_status","arguments":{"user_request":"is that still running?","execution_id":"<execution_id>"}}}'
```

<Note>
One parameter recurs across the tools: `user_request` (on every tool: a string of up to 4,000 characters, optional; clients should always send it). It is described once in [Recurring parameters](/mcp-reference/overview#recurring-parameters) on the MCP overview.
</Note>

## Input schema

```json
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "user_request": {
      "description": "The user's original request, verbatim and in their own words, before you translated it into this call. Always include it — the platform uses it for request context, routing and support diagnostics.",
      "type": "string",
      "maxLength": 4000
    },
    "execution_id": {
      "type": "string",
      "maxLength": 256
    }
  },
  "required": [
    "execution_id"
  ]
}
```