Connection health & troubleshooting

Every integration you connect depends on an authorization that Promptless holds on your behalf. When that authorization lapses, the integration stops working quietly. No error lands in your inbox, so the first sign is usually work that simply isn’t happening. This page shows you where to check the state of your connections and how to restore one that has gone stale.

Where to check connection health

Organization administrators manage every connected integration from the integrations page in the Promptless dashboard. Each integration has a card that shows its connection status and authentication state, along with controls to reconnect, refresh, or disconnect it.

When a connection needs attention, its card flags the problem so you can act on it. For example, a Slack card whose permissions are out of date shows a Needs reconnect flag. Whenever an integration seems to have stopped working, open the integrations page first—the card tells you whether the connection itself is the cause.

Note

The integrations page and its reconnect, refresh, and disconnect controls are available to organization administrators. If you’re not an admin, flag the integration to your Promptless administrator so they can check and reconnect it.

How a lost connection shows up

What you notice depends on what the integration does for you:

• Triggers are how events reach Promptless. If a trigger integration loses access, Promptless stops receiving its events, so no new suggestions come from that source—even when the rest of your setup looks healthy. Check for a lapsed connection whenever an expected suggestion never appears.
• Context sources are read-only and optional. If a context source loses access, Promptless still creates suggestions, but it can no longer pull in the background that source provided, so those suggestions draw on less context than usual.
• Publishing to GitHub needs an active connection with repository access. Without it, your repositories don’t appear in the dropdown when you set up a doc collection, and Promptless has nowhere to open documentation pull requests.

Tip

During a pilot, a healthy stream of suggestions is a signal that Promptless is plugged into the right parts of your workflow. If that stream dries up, confirm your trigger integrations are still connected before assuming the problem is elsewhere. See Run a pilot for more on reading suggestion volume.

Common symptoms and fixes

An expected suggestion never appeared

Check that the trigger integration for that source is still connected on the integrations page, and that its card isn’t flagging a reconnect. A trigger that has lost access stops delivering events to Promptless, so no suggestion is generated from it.

No repositories appear when creating a doc collection

If the repository dropdown shows “No options,” connect GitHub first from the integrations page. If GitHub is already connected but repositories are missing, grant Promptless access to those specific repositories in your GitHub organization settings. See GitHub repos (docs as code) for the full flow.

Slack diff files or link previews stopped working

When a Slack feature stops working, your workspace is usually missing a permission that a newer version of Promptless needs. Click Reconnect on the connected Slack card to approve the current permissions. See Slack troubleshooting for the specific permissions behind attached diff files and link previews.

When to contact support

If a card doesn’t show a reconnect option, reconnecting doesn’t resolve the problem, or you’re unsure which integration is at fault, contact the Promptless team at help@gopromptless.ai. See Getting help for every way to get in touch.

To retire a connection instead of fixing it, disconnect the integration from its card on the integrations page, which immediately revokes Promptless’s access to that service. For how Promptless accesses and retains data from connected services, see Data handling and classification.