An integration isn't receiving events
Jaah talks to other systems in two directions: it acts on them through connections (your Git accounts, your organization's Slack, credentials), and it hears from them through automations that wait for an event. Find the direction that broke.
A Git account stopped working
Symptom: tasks can't clone or push, or a task waits and names a Git account to connect. Your profile's Git section shows Needs reconnect on a row.
Cause: the token was revoked or expired on the Git host, or you lost access to the repository.
Fix:
- Select your initials at the bottom of the sidebar, then My Profile, then Git.
- Hover Needs reconnect for the reason.
- Open the row's ⋯ menu and select Reconnect, then approve on the Git host.
- If GitHub opens the Jaah GitHub App's install page, an owner of the repository's GitHub organization installs it there; anyone else selects to request an owner's approval and waits for it.
- Start the waiting task again with Start.
The tab is described in Your profile.
An automation doesn't fire on an event
Symptom: something happens on GitHub, a tracker or another system, but the automation's Runs tab shows no new Event delivery.
Cause: the event never reached Jaah: the webhook on the other system is missing, points to an old address, uses an old secret or key, or doesn't send that event. Or the automation is Paused.
Fix:
- Open the automation under Audit > Automations. If its status is Paused, resume it: see Run, pause or change an automation.
- On Setup, under Endpoint, select Copy URL, and check the webhook on the other system uses that exact address.
- For GitHub, check the repository's webhook against what Endpoint lists field by field, including the events to tick. Check When names those Events and Actions.
- For a Webhook automation (such as one a tracker calls), check each call sends
Authorization: Bearerwith an API key that holds Tasks: create. A row saying Legacy secret. Switch to an API key. should be switched. - If the secret was lost, select Rotate secret, then paste the new one into the other system.
- Send a test event from the other system, then open Runs: a new run appears. On Advanced, Test shows the task a sample payload would file.
If a run appears but files nothing, open it: Targets names the reason, such as a skipped or Not reached target. Dedup entries on Advanced lists events already filed, so a repeat is dropped; Clear forgets one.
Slack alerts stopped
Symptom: no alerts in Slack, or the Alerts section of your Preferences shows Reconnect Slack or Wrong workspace on a Slack row.
Cause: your organization's Slack workspace was disconnected or the Jaah app was removed from Slack (Uninstalled in Slack.), or your row was linked in another workspace.
Fix:
- Reconnect Slack: an Org Owner or Org Admin opens Settings > Integrations, the Slack card, and selects Add to Slack (or Reconnect), then Allow in Slack.
- Wrong workspace: on a Slack DM row, open ⋯ and select Reconnect; for a Slack channel, remove it and add it again.
- A private channel isn't listed until the Jaah app is invited to it in Slack.
The steps are in Connect Slack.
A tracker or another service refuses Jaah
Symptom: a task that reads or updates Jira or another service fails, naming an authentication error.
Cause: the credential the project uses for it holds an expired or revoked token.
Fix: create a new token on that service, then replace the credential's value under Directory > Secrets: see Replace or delete a credential. Start the task again.
Related
- How automations work — events, runs and skips.
- Automations — every field of Setup, Runs and Advanced.
- How credentials work — where a connection's secret lives.