> ## Documentation Index
> Fetch the complete documentation index at: /docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting

> Fixes for the most common setup problems.

## Detect

> **Ordyn didn't review my pull request**
>
> Check that the PR is on your **default repository** (GitHub connection settings), is not a draft, and was not opened by a bot. Then check the **Rules** in Detect settings for author or path filters that exclude it. A PR with the `struct:skip` label is skipped on purpose.

> **Monitors weren't created after a deploy**
>
> Ordyn only acts on deploys to the environment named in Detect settings, and the name must match exactly, including case. If you use GitHub Deployments, confirm the deploy job sets `environment:` and the GitHub App has the Deployments permission. If you use GitHub Workflow, confirm the repository webhook exists and is subscribed to Workflow runs, and that the chosen workflow completed successfully. If you use Other Webhook, confirm the post reached Ordyn with a deployment key. Monitor creation can take up to about an hour while Ordyn waits for real telemetry.

> **A monitor shows a permission error**
>
> Ordyn needs write access in the provider to create monitors. Open Detect settings and check the grant for that provider. The **Action required** view in Detect lists every provider access problem.

## Triage and Slack

> **Ordyn doesn't respond in Slack**
>
> Ordyn must be invited to the channel and the Slack connection must be active in **Connections**. Ordyn does not respond in shared channels from other workspaces.

> **Alerts in my channel aren't being investigated**
>
> Turn on **Auto-investigate** for that channel on the **Triage** page. If keyword filters are set, they decide what runs. Ordyn also skips messages inside threads and its own messages.

> **An alert fired but nothing posted to Slack**
>
> Check the **Episodes** page. If the alert was graded below the channel's sensitivity floor, it was held on purpose. Lower the sensitivity, or reply on a related thread and tell Ordyn to always notify for that monitor.

> **Ordyn ignored my request in a thread**
>
> Ordyn acts only on messages from people who are members of the channel. Mention Ordyn directly in the alert's thread and state the change you want.

## Fix and coding agents

> **No PR after clicking Create PR**
>
> Check that the GitHub App is installed on the target repository with permission to create branches and pull requests. Branch protection rules that require signed commits can also block it.

> **The PR's tests fail**
>
> Ordyn runs your post-execution script and iterates when it fails, but it can only catch what the script catches. Match the script to your CI on the **Fix** page.

> **MCP server won't connect**
>
> Re-copy the install command from **Settings → Workspace** and make sure you used the URL shown there. Then run `struct login` and try again.

## Integrations

> **Datadog returns 403**
>
> Datadog checks permissions on the **application key's** role, not the API key. Compare the role against the full scope list on the [Datadog](/integrations/datadog) page. A 403 on metrics only usually means `timeseries_query` is missing. A 403 while setting up Auto Monitors usually means one of the write scopes is missing.

> **Log queries come back empty**
>
> Confirm the credential can read the log group, workspace, or project you expect, and that the region is right. Ordyn only sees what the credential sees.

> **Ordyn can't see my repository**
>
> Open **Connections → GitHub** and check the repository is enabled for the Ordyn GitHub App. Some organizations require an admin to approve the installation.

Still stuck? Email [help@ordyn.dev](mailto:help@ordyn.dev).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.