You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: apps/sim/content/blog/v0-5/index.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -63,7 +63,7 @@ The dashboard aggregates this data into queryable views:
63
63
-**Trace spans**: Hierarchical view of block executions with timing waterfall
64
64
-**Cost attribution**: Token usage and spend broken down by model per execution
65
65
-**Error context**: Full stack traces with the block, input values, and failure reason
66
-
-**Filtering**: Query by time range, trigger type (webhook, schedule, API, manual), workflow, or status
66
+
-**Filtering**: Query by time range, trigger type, workflow, or status
67
67
-**Execution snapshots**: Each run captures the workflow state at execution time—restore to see exactly what was running
68
68
69
69
This level of observability is necessary when workflows handle production traffic—sending customer emails, processing payments, or making API calls on behalf of users.
0 commit comments