Every connection in DIJJI.ai carries a small health badge that tells you, at a glance, whether it’s working. When something is wrong, the badge is usually the first place you’ll see it. This page explains what each state means and what to do about it. For removing and re-adding a connection, see Disconnect or reconnect an integration.
The connections that show health are GitHub, Jira, and Slack. GitHub and Jira sit on the Integrations page and use the same three labels; Slack is shown per project and uses its own — so this page covers them separately.
GitHub connection health
On the Integrations page, each connected GitHub account on the GitHub card shows a coloured health badge next to its name, along with its repository count and a Last sync time. The badge has three states:
- Healthy (green) — the connection is working normally. DIJJI.ai can reach the account, read its repositories, and open pull requests. Nothing to do.
- Degraded (amber) — the connection is working but something needs attention. This often clears on its own; check the Last sync time and look again shortly before taking any action.
- Disconnected (red) — DIJJI.ai can no longer reach the account. Projects bound to it can’t sync issues or open pull requests until the connection is restored.
The Last sync time sits beside the badge — “Just now”, “5m ago”, “2h ago”, “3d ago”, or Never if the account has not synced yet. A stale Last sync alongside a Degraded badge is a sign the connection has been having trouble for a while.
What to do about a GitHub connection
- Healthy — nothing. To review or change which repositories the account shares, use Manage on the card; that opens the account’s installation settings on GitHub without touching the connection.
- Degraded — wait and check back. If it doesn’t return to Healthy, treat it like Disconnected.
- Disconnected — reconnect the account. Select Disconnect to release it cleanly, then Add account to set it up fresh. The full steps are in Disconnect or reconnect an integration.
Jira connection health
A connected Jira site shows the same health badge as GitHub, in the same place on the Integrations page, with the same three states — Healthy, Degraded, and Disconnected. Read and act on them exactly as for GitHub above: a Disconnected Jira site can’t sync issues into tasks until you reconnect it. See Connect Jira for the connection itself.
Slack notification health
Slack health is shown per project, not for the whole organization. Open a project’s Settings tab and find the Slack Notifications card. The Status row shows one of three states, and a Last delivery row shows when DIJJI.ai last tried to post a message:
- Active (green) — DIJJI.ai is posting run updates to the channel normally.
- Degraded (amber) — a recent message didn’t get through, but the failure looks temporary (for example, Slack was rate-limiting or briefly unavailable). DIJJI.ai keeps retrying, and the state often returns to Active on its own. The badge may show a short detail in brackets, such as Degraded (429).
- Broken (red) — delivery is failing in a way that won’t fix itself, so DIJJI.ai stops sending to this channel. The badge shows the reason after a colon — for example Broken: channel_not_found or Broken: invalid_token.
A Broken connection is skipped entirely — no run updates reach Slack until you fix it. Degraded still delivers; it’s just warning you that a recent attempt failed.
What to do about a Slack connection
-
Active — nothing.
-
Degraded — give it a little time; retries usually clear it. To check sooner, use Send test on the card — a successful test message returns the status to Active.
-
Broken — the webhook itself needs fixing. The reason on the badge tells you what’s wrong:
- channel_not_found or channel_is_archived — the target channel no longer exists or was archived. Pick a live channel in Slack and create a fresh webhook for it.
- invalid_token or no_service — the webhook URL is no longer valid. Recreate the Incoming Webhook in Slack.
In every case, the fix is the same on the DIJJI.ai side: use Update on the Slack Notifications card to enter the new webhook URL. Updating the webhook resets the status to Active. You can then use Send test to confirm a message gets through. See Set up Slack notifications for a project for the full webhook steps.
A quick way to read the badges
If a connection’s badge is green, you don’t need to do anything. Amber means watch it — it’s usually temporary, and a test or a short wait will tell you. Red means act — a GitHub account needs reconnecting, and a Slack channel needs a new webhook before run updates will reach it again.