4 synthetic rows in workflow_timeline_events. The sample timestamps shift to match the query window when the data loads.
Queries return up to 500 rows. The sample data is synthetic.
The sample data and query stay in your browser.
Expected result
Query results and chart
Query result
Failed workflow event timeline
Shipment creation fails 47 seconds after the workflow begins, after payment and inventory both succeed.
| workflow_id | step_number | event_name | service | status | elapsed_seconds |
|---|---|---|---|---|---|
| workflow_1024 | 1 | workflow_started | checkout-api | ok | 0 |
| workflow_1024 | 2 | payment_authorized | checkout-api | ok | 8 |
| workflow_1024 | 3 | inventory_reserved | fulfillment-worker | ok | 21 |
| workflow_1024 | 4 | shipment_created | fulfillment-worker | failed | 47 |
Synthetic example output. Run the query against your own event schema and thresholds before using it for operational decisions.
Need joins and a learning path?
Practice joins with a SaaS dataset
The SQL Lab connects accounts, product events, API requests, LLM requests, jobs, and billing events across five guided analyses.
What the playground checks
The playground checks that the read-only query runs on the sample rows and returns the expected result. When you first run a query, your browser downloads a specific DuckDB version from jsDelivr. It does not send your SQL or sample data with that request. Telemetry recipes are separately planned with Apache DataFusion, the engine used by Telemetry. DuckDB and DataFusion are distinct SQL engines, so validate any edited syntax with the SQL reference before using it in production.