Stream States and Lifecycle
Every stream config can have many runs. The config rail groups those runs by outcome; opening one shows its Monitor, Compare, Logs, and the next available action.
Use the Dashboard and UI Guide for the visual walkthrough of the run rail and monitor.
Stream states
| State | Terminal | Success | Description |
|---|---|---|---|
READY | No | — | Stream exists but has not started yet |
RUNNING | No | — | Actively reading from source and writing to target |
PAUSED | No | — | Temporarily suspended; can be resumed via API (POST /streams/{id}/resume) |
FINISHED | Yes | Yes | Completed successfully — normal terminal state for Load workflows |
TIME_LIMIT_REACHED | Yes | Yes | Stopped after reaching the configured elapsedTime limit |
EVENT_LIMIT_REACHED | Yes | Yes | Stopped after reaching the configured numberOfEvents limit |
STOPPED | Yes | No | Stopped intentionally by the user; the monitor preserves the progress reached at the stop point |
FAILED | Yes | No | Ended because of an error (connectivity, permissions, invalid SQL, write failures) |
Common state transitions
Typical Load flow:
READY -> RUNNING -> FINISHED
Typical bounded run:
READY -> RUNNING -> TIME_LIMIT_REACHED
READY -> RUNNING -> EVENT_LIMIT_REACHED
Typical interrupted run:
READY -> RUNNING -> PAUSED
READY -> RUNNING -> STOPPED
READY -> RUNNING -> FAILED
What to do after a terminal run
Only FINISHED, TIME_LIMIT_REACHED, and EVENT_LIMIT_REACHED count as successful completions. STOPPED is terminal but not successful; it means the run ended before its natural completion.
- Finished — review the monitor or Compare result, then use Run Again only when you need another execution.
- Stopped — inspect the saved Load progress. An eligible saved state exposes Resume Load; otherwise use Reset to clear incompatible saved state before starting fresh.
- Failed — open Logs and the failure summary. Fix the cause before using the action shown in the header.
Troubleshooting by state
FAILED
Check:
- source and target connectivity
- permissions and replication prerequisites
- query validity if custom SQL is involved
- runtime logs in Observability
PAUSED or STOPPED
Check the Monitor first. For Load, its saved chunks and the header action tell you whether the run can resume or must be reset.
TIME_LIMIT_REACHED or EVENT_LIMIT_REACHED
Confirm whether the limit was intentional. If not, adjust the stream configuration before the next run.