Skip to content

For the complete documentation index, see llms.txt.

Connection health & troubleshooting

Every integration you connect depends on an authorization that Promptless holds on your behalf. When that authorization lapses or lacks a permission, the work that depends on it stops. If your organization has an escalation channel configured, Promptless reports the problem there. Otherwise, the first sign is usually work that isn’t happening. This page lists those signs, what causes each one, and how to restore the connection.

Whenever an integration seems to have stopped working, start on the integrations page in the Promptless dashboard. Each integration’s card shows a health label:

LabelWhat it meansWhat to do
ConnectedThe latest check succeeded.No action needed.
ProblemPromptless couldn’t verify the integration, or the service was unreachable, during the latest check.No action needed. Promptless checks again automatically.
Needs reconnectThe authorization expired or was disconnected.Reconnect the integration from its card.

Symptom: An expected suggestion never appeared

Section titled “Symptom: An expected suggestion never appeared”

Cause: The trigger integration lost access

Section titled “Cause: The trigger integration lost access”

Triggers are how events reach Promptless. When a trigger integration loses access, Promptless stops receiving its events, so no new suggestions come from that source. The rest of your setup can look healthy while this happens.

Solution: Reconnect the trigger integration

Section titled “Solution: Reconnect the trigger integration”
  1. On the integrations page, find the card for the integration that sends the trigger.

  2. If the card shows Needs reconnect, select its reconnect action and approve access with the provider.

Symptom: A trigger type is disabled, or a saved trigger appears inactive

Section titled “Symptom: A trigger type is disabled, or a saved trigger appears inactive”

Cause: The trigger’s provider isn’t connected

Section titled “Cause: The trigger’s provider isn’t connected”

In the configuration editor, a provider’s trigger type is available only while that provider is connected. Its saved triggers show as inactive until then. See Provider connection and trigger availability.

Symptom: No repositories appear when you add a doc collection

Section titled “Symptom: No repositories appear when you add a doc collection”

When you add a doc collection, the repository picker shows “No connected repository matches that.” The picker lists only repositories that your GitHub or GitLab connection can reach. Promptless needs the same access to open documentation pull requests.

The picker lists none of your repositories.

  1. On the integrations page, connect GitHub or GitLab.

  2. Return to the doc collection and select the repository.

For the full flow, see GitHub repos (docs as code) or GitLab projects.

Cause: The connection can’t reach that repository

Section titled “Cause: The connection can’t reach that repository”

Other repositories appear in the picker, but not the one you want.

  • For GitHub, add the repository to the Promptless GitHub App’s access in your GitHub organization settings. See Manage repository access.
  • For GitLab, connect a group access token from a group that contains the project. See Token scope considerations.
Section titled “Symptom: Slack link previews, MCP result DMs, or private channel listing stopped working”

Cause: The Slack connection is missing a newer permission

Section titled “Cause: The Slack connection is missing a newer permission”

Some Slack features need permissions that Promptless added after your workspace connected. When your workspace is missing one, the Slack card shows a Grant additional Slack permissions callout that names the permissions to add. See Slack troubleshooting for the permissions behind file uploads, link previews, MCP result DMs, and private channel listing.

  1. On the Slack card, in the Grant additional Slack permissions callout, select Update connection.

  2. In Slack, approve the added permissions.

Symptom: A Jira reply or comment from Promptless didn’t post

Section titled “Symptom: A Jira reply or comment from Promptless didn’t post”

Cause: Atlassian refuses the service account’s credential

Section titled “Cause: Atlassian refuses the service account’s credential”

When the Atlassian card’s service-account health badge reads Not working, Atlassian is refusing the service account’s credential. Promptless then can’t post as its bot identity. The service-account credential is separate from the Atlassian OAuth connection, so reconnecting Atlassian leaves the credential unchanged.

Cause: No service account is attached and Promptless lacks permission to comment

Section titled “Cause: No service account is attached and Promptless lacks permission to comment”

With no service account attached, Promptless comments as the person who connected Atlassian only when your Knowledge Base or the request explicitly permits it. Otherwise it skips the comment and sends the result to your other notification channels. A session started by a promptless label or a configured trigger also posts no comment when there’s no documentation change.

Solution: Attach a service account or permit comments

Section titled “Solution: Attach a service account or permit comments”

Symptom: Suggestions draw on less context than usual

Section titled “Symptom: Suggestions draw on less context than usual”

Context sources are read-only and optional. When one loses access, Promptless still creates suggestions, but without the background that source provided.

  1. On the integrations page, find the context source’s card.

  2. If the card shows Needs reconnect, select its reconnect action and approve access with the provider.

  • Contact the Promptless team at help@gopromptless.ai if a card doesn’t show a reconnect option or reconnecting doesn’t resolve the problem. Also reach out if you’re unsure which integration is at fault. See Get support for every way to get in touch.
  • To retire a connection, disconnect the integration from its card on the integrations page. Disconnecting immediately revokes Promptless’s access to that service. For how Promptless accesses and retains data from connected services, see Data handling and classification.