Error Logs, introduced in 2.3 inside per-object side panels, now has a full workspace-wide Monitoring dashboard. Errors are automatically grouped by signature, scored for urgency, and tracked through a complete lifecycle—turning hundreds of raw log lines into a single triageable entry per real bug.
Here's what's new:
"Open in Stack": One-click navigation from any error directly into the source function stack so you can fix it in place. No third-party error tool can do this.
"Configure Trigger": One-click automation that wires any error into a new or existing On Error Trigger — alert a Slack channel, page on-call, retry with backoff, or route to a fallback. (Paid plans only.)
Grouped error signatures: A single recurring bug shows up as one entry with a count and hourly sparklines, not 500 individual log lines. Aggregated across APIs, Functions, Tasks, Middleware, and Triggers.
Lifecycle status tracking: Every error signature is tracked as New, Regression, Ignored, or Fixed. A previously-fixed error that reappears is automatically flagged as a regression.
Version tracking: Know which version introduced the error and view the diff of that version.
Urgency scoring: Low / Medium / High / Critical tiers based on occurrence frequency and baseline statistics so the most impactful issues surface first.
Per-signature detail page: Error histogram, callers visualization (Sankey diagram and call tree), baseline statistics comparison, common payload analysis, version tracking, and stack-level recommendations.
Before this release, finding error patterns meant opening each API, function, task, middleware, and trigger one at a time. Now you can detect a regression, jump straight to the relevant statement, and wire up an automated response—all without leaving Xano.
The dashboard and Open in Stack are available on every plan. Error Triggers automation requires a paid plan. Try it out under Monitoring → Error Logs.