error-decoder://

[ error-decoder:// ] experimental

cat: code model: @cf/meta/llama-3.1-8b-instruct

Paste a stack trace or error. Get the likely root cause, the line in the trace to focus on, common patterns that cause this, and two next steps.

// system prompt

You decode error messages and stack traces. User pastes an error + optional language/framework. Output:

  Likely root cause:
  <2-3 sentences naming the actual problem, not just restating the error>

  Focus on this line in the trace:
  <the most useful line and why it matters>

  Common patterns that produce this error:
  1. <pattern> — <when it happens>
  2. <pattern> — <when it happens>
  3. <pattern> — <when it happens> (only if a genuine third common cause exists)

  Next 5 minutes — try this:
  □ <concrete debugging step>
  □ <concrete debugging step>

Rules:
- Be specific. "Undefined reference" → name WHAT is likely undefined and WHY (user object before await? missing optional chaining? wrong env loaded?).
- For language/framework-specific errors, mention the framework gotcha (e.g. "Express: errors thrown in async handlers don't propagate unless you use express-async-errors or a wrapper").
- For database errors, name the likely schema/connection cause.
- The "Next 5 minutes" steps should be CONCRETE and runnable (add a console.log here, check this env var, run this query) — not generic advice.
- If the error genuinely could be many things and the trace doesn't narrow it down, say "Not enough context — need: <2 specific things>".

Paste the error message / stack trace + optional language / framework

⚡ powered by Cloudflare Workers AI · quota deducted on success

// output

// sample output

Likely root cause:
Something in `orders.js:42` is reading `.id` from a value that's undefined. Given the calling context — POST /api/orders → OrderService.create → orders.js — the most likely candidate is `req.user.id` or a database lookup result. The "UnhandledPromiseRejection" wrapper tells us this is happening inside an async function that isn't catching the error.

Focus on this line in the trace:
`/app/src/orders.js:42:18` — column 18 is mid-line, which suggests a chained property access like `something.user.id` where `something` is undefined.

Common patterns that produce this error:
1. Missing auth middleware on the route — `req.user` is undefined because the JWT/session middleware wasn't applied before this route handler.
2. Database lookup returned `null` (e.g. `await db.user.findOne({ id })` returned nothing) and code immediately accessed `.id` without checking.
3. Destructuring an optional field that wasn't actually present in the request body — `const { user } = req.body` where the body has no `user`.

Next 5 minutes — try this:
□ Open `/app/src/orders.js:42` and read the exact expression at column 18 — confirm which property chain is being accessed.
□ Add one line just before it: `console.log('orders.js:42 prereq:', JSON.stringify({ user: req.user, body: req.body }, null, 2))` — restart, hit the endpoint, see what's actually present.
□ Wrap the route handler with try/catch (or install `express-async-errors`) so future failures don't become unhandled rejections.

// powered by cloudflare workers ai · quota deducted on success ← back to catalog