Code Reliability settings and troubleshooting

Most Code Reliability problems come from connector access, incorrect source mapping, stale synchronization, or missing repository permissions.

Quick checks

Symptom	Check first
No detections	Connector health, source scope, and last sync
Wrong repository	Source Mapping and service ownership
Stale pattern count	Last activity, filters, and Re-generate
Missing Slack update	Workspace connection, channel, and bot membership
Fix Now unavailable	Pattern eligibility, role, and repository write access
Generated PR missing	Target repository, job status, and provider permissions
Audit stays queued	Repository access, branch, and repository size
Score changed unexpectedly	Branch, audit date, scope, and issue-level differences

Safe recovery

Record the current state before regeneration or broad remapping. Test with one repository or pattern, keep source-system evidence, and verify the result before expanding the change. When contacting support, include the workspace, repository, source, pattern or audit ID, UTC timestamp, selected filters, and a redacted error. Never include credentials or sensitive log values.

Investigate, fix, and monitor

Automations

⌘I

Get started

Products

Integrations & deployment

Workspace administration

Enterprise & trust

Reference & support

Code Reliability settings and troubleshooting

Quick checks

Safe recovery

​Quick checks

​Safe recovery

Quick checks

Safe recovery