---
title: "Stream Workflow Events"
method: GET
path: "/workflow/{workflow_run_id}/events"
tags: ["Workflow Runs"]
---

# Stream Workflow Events

`GET /workflow/{workflow_run_id}/events`

**Available for**: Chatflow, Workflow apps.

Resume the Server-Sent Events stream for a workflow run after a pause or a dropped SSE connection. For runs that have already finished, the stream emits a single `workflow_finished` event and closes.

To check an in-progress run's node-level status and progress, call it with `include_state_snapshot=true`: the stream replays each already-executed node's status before streaming new events.

## Path parameters

- `workflow_run_id` string, uuid, required

## Query parameters

- `user` string, required
- `include_state_snapshot` boolean
- `continue_on_pause` boolean

## Response `200`

Server-Sent Events stream. It opens with a bare `event: ping` frame (keep-alive; more arrive roughly every 10 seconds); every other event is delivered as `data: {JSON}\n\n`. Event payloads follow the same schemas as the original streaming response.

## Other responses

- `400` — `not_workflow_app` : Please check if your app mode matches the right API route.
- `404` — `not_found` : Workflow run not found.

---

[API](https://skmtc.net/langgenius/apis/dify-service-api.md) · [All operations](https://skmtc.net/langgenius/apis/dify-service-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/langgenius/dify-service-api/revisions/e49b3db72bad/schema)