Run statuses
How a run is triggered
- Manual — a user starts it from the app.
- Scheduled — it runs automatically on a schedule.
- API — it’s started by an external call.
What a run shows
- Status and the trigger type (manual / scheduled / API).
- Who triggered it — the user, when applicable.
- Timing — when it was requested, started, and completed.
- Structured logs — timestamped entries at
Debug,Info,Warn, andErrorlevels emitted during the import. - Error message — a readable explanation when a run fails.
Working with ingestion runs
1
Open the runs page
Go to Data platform → Data sources → Ingestion runs to see the history of all
imports. Filter by status, date range, trigger type, or who started the run.
2
Start a run
Trigger a new import with Run ingestion. Its status moves from Pending to
Running, then to Success or Failed.
3
Inspect a run
Open a run to read its full logs, timing, and any error message in the detail view.
4
Diagnose failures
For a failed run, the error message and
Error-level log entries tell you what
went wrong so you can fix the source file or the
ingestion spec and retry.
