Promptless Now Alerts You When an Integration Has a Problem
Promptless now alerts you when a connected integration develops a problem. A broken connection no longer fails silently.
The problem
Section titled “The problem”When a Promptless integration breaks, documentation suggestions stop generating for any doc collection that depends on it. Before this change, there was no outbound signal. A teammate might notice the docs had not updated. Or you might discover the problem when you checked the dashboard after days of silence. The gap between failure and discovery could stretch to a week. Recovery work grows with every day the connection stays broken.
Integrations break for ordinary reasons, like an expired access token or a revoked Slack permission. A third-party provider can also have an outage. These problems are common and easy to fix once you notice them.
What changed
Section titled “What changed”Promptless now monitors the health of each connected integration. When a connection develops a problem, Promptless sends a notification to your organization’s configured escalation channels. Escalation channels can be Slack, Microsoft Teams, email, or any combination of these. The message names the specific integration. It also lists the doc collections that can no longer update.
Promptless uses two alert states.
Needs reconnect fires immediately when Promptless detects that an integration needs action, such as expired credentials or a revoked permission. You get one notification when Promptless first detects the problem.
Temporary outage fires only if the problem lasts more than 24 hours. Short outages usually resolve on their own. Promptless does not send an alert for those. If a temporary outage turns into a reconnect requirement, Promptless sends a follow-up alert.
In both cases you get one notification per problem. Promptless does not send a new notification every day the problem continues. Each message includes a reconnect link. You can act on it without opening the Integrations page first.
Who benefits most
Section titled “Who benefits most”This feature helps teams most when the person who configured an integration isn’t checking the dashboard. That describes most teams. A developer sets up the GitHub connection during onboarding. The auth token expires two months later. Nothing in the developer’s normal workflow reveals the problem. This alert sends that signal instead of waiting for someone to notice.
This feature also helps teams with documentation freshness requirements. A broken integration creates an undetected documentation gap. Each unresolved day adds more undocumented code changes. Catching the failure in hours instead of days limits the drift.
Notifications go to your organization’s escalation channels. Configure escalation channels in Organization Settings, under Notification channels. If you haven’t configured one, this is the only required step.
Once you configure escalation channels, integration health monitoring runs automatically. There’s no per-integration opt-in.
The Integrations page also shows a health badge for each connected service at any time. The alert notifies you automatically when something breaks. The Integrations page shows the current status when you check it yourself.