Application errors and logs
The web middleware integrates evlog. Shared error codes and localized messages come from packages/errors; its server handler logs unexpected failures while the client resolver returns a safe user message. During development, inspect .evlog/logs/ when available. Do not copy credentials, prompts or private payloads into logs.
Each RPC request has a request ID: cf-ray when Cloudflare set a well-formed one, otherwise a UUID. It is context.requestId on the server, the x-request-id header on every /api/rpc response (including the 500 when building the context fails), and a field of the error log. The MCP context derives its own requestId for the logs of its document tools; MCP responses do not carry the header. It serves only to correlate logs, never to decide anything: outside Cloudflare (local wrangler dev, Node) a client can send a well-formed cf-ray and it is used as is, and Cloudflare's header reference does not say whether a client-sent value is replaced. The error handler writes expected 4xx failures at debug level and unexpected ones (5xx, unknown codes, non-oRPC errors) as errors, both with the request ID, so a user's quoted header finds the matching line (error handling).
An Audit Event is a durable domain record, not a log line. The Audit Log is the admin table; an Activity Timeline is one User's security history. Release notes belong to the public changelog.
Worker traces
Wrangler enables observability and traces. The scheduled handler passes ctx.tracing into runScheduledJobs; workersTracer adapts Effect spans to Cloudflare spans. It records scalar attributes, failures and interruption.
The native API cannot assign an explicit parent to each Effect span. Those spans appear as siblings under jobs.scheduled, alongside platform fetch and Hyperdrive spans. Node execution runs without this tracer. Local successful jobs do not prove that production custom spans are visible in the Cloudflare dashboard.
Diagnose a failure
Trace the entry point, transport result and durable row together. For an import, inspect its state and persisted failure reason before assuming the queue lost it. For a webhook, inspect the delivery lease and next attempt. For a client error, keep the stable error code and correlation context rather than exposing an exception message.
Bundle and fault experiments are recorded in docs/measurements. Their local timings are not production latency or billing measurements. Add a dated report when changing runtime ownership, deadlines or a heavy dependency.