A connection in DIJJI.ai is showing something other than a green badge — Degraded, Disconnected, or Broken — and you want to know what broke and how to fix it. This page is the troubleshooting walk-through.
For what each state means in full, see Read integration health states. For the steps to remove and re-add a connection, see Disconnect or reconnect an integration.
GitHub, Jira, and Slack are the connections that show health. GitHub and Jira use the same labels and live on the Integrations page; Slack is shown per project — so check the one that’s troubling you.
GitHub: the connection isn’t healthy
Open Integrations and look at the GitHub card. Each connected account shows a coloured health badge, a repository count, and a Last sync time.
Degraded (amber)
The connection is working but something needs attention. This usually clears on its own.
- What it stops: nothing yet — issues still sync and pull requests still open. Degraded is a warning, not an outage.
- What to do: wait, then check the badge again. Glance at the Last sync time too — a recent sync alongside Degraded means it’s a passing wobble; a stale Last sync means it’s been struggling for a while. If it doesn’t return to Healthy, treat it as Disconnected and reconnect.
Disconnected (red)
DIJJI.ai can no longer reach the account.
- What it stops: projects bound to that account can’t sync new issues or open pull requests until it’s restored. This is also why a
dijji-labelled issue might not appear as a task — see My issue didn’t sync. - Common causes: the GitHub App was uninstalled or suspended on the GitHub side, its access was revoked, or repository permissions were changed so DIJJI.ai lost reach.
- The fix: reconnect the account. On the GitHub card, select Disconnect to release it cleanly, then Add account and go through the install flow again — choose the account, choose which repositories to share, and confirm. Full steps are in Disconnect or reconnect an integration.
Reconnecting is an admin action. If you don’t have the admin role, ask an admin on your organization to do it.
Jira: the connection isn’t healthy
A Jira site shows the same Degraded and Disconnected badges as GitHub, on the Integrations page, and you fix them the same way: Degraded usually clears on its own; Disconnected means DIJJI.ai has lost access — often because the Jira authorization was revoked on the Jira side — and projects bound to it can’t sync issues until you reconnect it from the Jira card. Reconnecting is an admin action. See Connect Jira.
Slack: notifications aren’t getting through
Slack health is shown per project, not for the whole organization. Open the project’s Settings tab and find the Slack Notifications card. The Status row shows the state; a Last delivery row shows when DIJJI.ai last tried to post.
Degraded (amber)
A recent message didn’t get through, but the failure looks temporary — Slack was rate-limiting or briefly unavailable.
- What it stops: nothing. DIJJI.ai keeps retrying and messages still go out; it’s just flagging a recent miss. The badge may show a short detail such as Degraded (429).
- What to do: give it a little time — retries usually clear it back to Active. To check sooner, use Send test on the card; a successful test returns the status to Active.
Broken (red)
Delivery is failing in a way that won’t fix itself, so DIJJI.ai stops sending to this channel entirely — no run updates reach Slack until you fix it. The badge shows the reason after a colon.
| Badge reason | What’s wrong | The fix |
|---|---|---|
channel_not_found | The target channel no longer exists | Pick a live channel in Slack, create a fresh Incoming Webhook for it |
channel_is_archived | The channel was archived | Unarchive it, or pick a different channel and create a new webhook |
invalid_token | The webhook URL is no longer valid | Recreate the Incoming Webhook in Slack |
no_service | The webhook is no longer recognised | Recreate the Incoming Webhook in Slack |
In every case the DIJJI.ai-side fix is the same: use Update on the Slack Notifications card to enter the new webhook URL. Updating it resets the status to Active. Then use Send test to confirm a message gets through. Full webhook steps are in Set up Slack notifications for a project.
A quick way to decide what to do
- Amber (Degraded) — watch it. Usually temporary; a short wait or a test will tell you.
- Red (Disconnected / Broken) — act. A GitHub account needs reconnecting; a Slack channel needs a fresh webhook before updates flow again.
Still not healthy
If you’ve reconnected the GitHub account or updated the Slack webhook and the badge still isn’t green after a few minutes — reach out to DIJJI.ai support. Include the organization name, which connection it is (GitHub, Jira, or Slack), and the exact badge text, including anything after the colon.