Integration broken
For: an admin. Takes about 3 minutes.
What this means
Stacktic keeps a live connection to each tool you manage. That's how it knows who has access, who owns what, and whether an account is still active. When a connection breaks and Stacktic can't sync it anymore, it raises an Integration broken signal.
This fires on the connection's own status, not on one bad sync. A single slow request or a temporary hiccup from the vendor doesn't trigger it. This signal only shows up when Stacktic has given up and needs a person to step in. That happens for one of two reasons:
- the credential was rejected;
- the connection failed the same way several times in a row.
Why it matters
While a connection is broken, Stacktic can't see what's changing on that tool. Access changes, new admins, ownership changes: none of it gets picked up until the connection is reconnected. If someone leaves the company while the tool's connection is broken, offboarding won't catch their access on that tool either.
What you'll see
The signal names the tool and the reason Stacktic gives for the failure. For example, a rejected credential or a repeated connection error. It's assigned to the account's owner. Every Owner and Admin can see it on the Signals page in Stacktic, whoever it's assigned to.
Severity is always Critical. There's no early-warning stage for this one, because by the time it fires, the connection is already down.
What you can do about it
Open the signal and use the Open Integration tab button. Or go to the tool directly and open its Integration tab. From there:
- Reconnect it. If the tool is still one you use, reconnect with a valid credential. Once Stacktic completes a sync successfully, the signal clears on its own.
- Disconnect it. If you're retiring this tool, or its connection was never really needed, disconnect it from the Integration tab instead. That closes the signal too. Stacktic marks it as resolved because the connection was removed, not because anything was fixed. Either way, the change is visible in the signal's history.
How it's different from "Integration credential expiring"
You might also see an Integration credential expiring signal on a tool. That one is a warning. It fires before a token or key expires, so you have time to rotate it before anything breaks.
Integration broken is what happens after something already broke. Either the credential was rejected, or the connection failed enough times in a row that Stacktic stopped retrying.
They don't both fire on the same connection at once. Once a credential actually expires, the expiring-credential warning clears and Integration broken takes over.
Frequently asked questions
Why didn't this fire the first time a sync failed? A single failed sync usually means a temporary problem on the vendor's side. It clears itself on the next retry. Stacktic only raises this signal once it's confident the connection genuinely needs a person. That means either the credential itself was rejected, or the same kind of failure happened several times in a row.
I reconnected it. Why is the signal still showing? Give it a few minutes. The signal clears once Stacktic completes a sync against the new credential, not the instant you save the new connection. That way, the signal clearing is proof the fix actually worked, not just that you tried something.
Can I turn this signal off? Yes, in Settings → Signals, the same as any other signal type. If you turn it off, an admin has to notice a broken connection some other way. The Integration tab still shows it, just without the reminder in your task list.