Issues

Issues provides built-in error monitoring for Cloudflare Workers. It detects production failures and groups related failures into issues without an SDK or application wrapper.

Issues overview showing occurrence totals and active and resolved issues.

Enable source maps so captured JavaScript and TypeScript exception stacks point to the original files and lines. Framework builds must generate maps as well as upload them.

How Issues works

When a Worker throws an uncaught exception, fails an invocation, returns a 5xx response, or logs an error, Issues records the failure as an occurrence. It groups related occurrences from the same Worker into one issue.

Use the Issues overview to identify recurring failures and changes in activity. To review the diagnostic context for a failure, refer to Investigate issues.

You can also create an automation to automatically send an issue to a coding agent, webhook, chat service, or incident-management tool.

Enable Issues

You can enable Issues through Wrangler, the dashboard, or the Cloudflare CLI (cf).

Wrangler

Dashboard

Cloudflare CLI

Requires Wrangler 4.134.0 or later.

In your Worker's Wrangler configuration file, set observability.issues.enabled to true.

wrangler.jsonc

wrangler.toml

{
  "$schema": "./node_modules/wrangler/config-schema.json",
  "observability": {
    "issues": {
      "enabled": true
    }
  }
}

[observability.issues]
enabled = true

Deploy your Worker.

npm

yarn

pnpm

npx wrangler deploy

yarn wrangler deploy

pnpm wrangler deploy

Go to the Issues page.

dash.cloudflare.com
Select Enable issues.

Note

If you deploy with Wrangler, also set observability.issues.enabled to true in your Wrangler configuration file. Otherwise, the next deployment turns off Issues.

In your cloudflare.config.ts file, set worker.observability.issues.enabled to true.

cloudflare.config.ts

import { defineConfig } from "cf/config";
import * as entrypoint from "./src/index.ts" with { type: "cf-worker" };

export default defineConfig({
  worker: {
    name: "example-worker",
    entrypoint,
    compatibilityDate: "<COMPATIBILITY_DATE>",
    observability: {
      issues: {
        enabled: true,
      },
    },
  },
});

Deploy your Worker.
```
cf deploy
```

WranglerDashboardCloudflare CLI

Requires Wrangler 4.134.0 or later.

In your Worker's Wrangler configuration file, set observability.issues.enabled to true.

wrangler.jsonc

wrangler.toml

{
  "$schema": "./node_modules/wrangler/config-schema.json",
  "observability": {
    "issues": {
      "enabled": true
    }
  }
}

[observability.issues]
enabled = true

wrangler.jsoncwrangler.toml

{
  "$schema": "./node_modules/wrangler/config-schema.json",
  "observability": {
    "issues": {
      "enabled": true
    }
  }
}

Deploy your Worker.

npm

yarn

pnpm

npx wrangler deploy

yarn wrangler deploy

pnpm wrangler deploy

npmyarnpnpm

npx wrangler deploy

In your cloudflare.config.ts file, set worker.observability.issues.enabled to true.

cloudflare.config.ts

import { defineConfig } from "cf/config";
import * as entrypoint from "./src/index.ts" with { type: "cf-worker" };

export default defineConfig({
  worker: {
    name: "example-worker",
    entrypoint,
    compatibilityDate: "<COMPATIBILITY_DATE>",
    observability: {
      issues: {
        enabled: true,
      },
    },
  },
});

Deploy your Worker.
```
cf deploy
```

Issues processes new traffic after you enable it. It does not process historical failures. Send production traffic to the Worker, then open a detected issue in the Issues dashboard.

Report handled errors

To record an error that your application catches, pass the caught value to console.error() before returning a fallback response.

JavaScript

TypeScript

src/index.js

try {
	return await handleRequest(request);
} catch (error) {
	console.error(error);
	return new Response("Service unavailable", { status: 503 });
}

src/index.ts

try {
	return await handleRequest(request);
} catch (error) {
	console.error(error);
	return new Response("Service unavailable", { status: 503 });
}

JavaScriptTypeScript

src/index.js

try {
	return await handleRequest(request);
} catch (error) {
	console.error(error);
	return new Response("Service unavailable", { status: 503 });
}

Pricing

Issues is available to all Workers accounts in open beta. It is free to use during the beta period.

Limits

Limit	Value
Automations per account	50
Minimum occurrence threshold	1
Recurrence inactivity period	1 hour to 365 days
Completed automation-run history	30 days

How Issues works

Enable Issues

Report handled errors

Related resources

Pricing

Limits