Guides
Understanding Fallback Telemetry
Inspect fallback reasons, timeout/error classification, and usable vs unusable normalized results.
Need the shortest path?
Use Quick Start when you want the smallest working route → scan → graph → run flow first.
Something feels off?
Inspect scan output, graph state, active route/context, and dispatch in a practical order.
Need the full surface?
Browse all runtime methods, hooks, extension points, and lifecycle APIs.
Fallback should be observable, not mysterious.
Subscribe to fallback events
ts
7 lines
Cinder.on('fallback:start', (payload) => {
console.log(payload.reason, payload.provider, payload.timeoutMs);
});
Cinder.on('fallback:end', (payload) => {
console.log(payload.errorCode, payload.used, payload.latencyMs);
});What to inspect
fallback:start
Look at:
reasonproviderauthModetimeoutMs
fallback:end
Look at:
usednormalizederrorCodestatusCodelatencyMserrorMessage
Why this matters
Telemetry helps you tell the difference between:
- local unknowns
- provider/network failures
- timeout failures
- invalid provider responses
- normalization failures against the real graph
Related pages
Continue reading