Integrations tell you when they need reconnecting
When an integration loses access to the account it was connected to, you hear about it once — by email and in WA.cr — and its card says what to do. Store syncs are offered only where the integration really supports them.
Released 11 October 2026
An integration that stops working no longer fails quietly — WA.cr tells you, once, and its card shows what to do next.
What's new
- One notice when an integration needs reconnecting — if an integration loses access to the account it was connected to (a password change, revoked access, an expired sign-in), your workspace's owners and admins get one "Integration needs reconnecting" email and in-app notice, with a link straight to it.
- Cards show the problem in plain words — on the Integrations page, the card reads reconnect when it needs signing in again, or unhealthy with a short sentence for other problems, such as missing permissions or something it relies on no longer existing.
- No alert storms — repeated failures don't send repeated messages, and you never get more than one reconnect notice a day for the same integration. A brief slowdown at the other service tells nobody anything.
- Integrations built by WA.cr Partners report their health too — so a Partner integration that stops working shows up the same way as one built by WA.cr.
- Syncs are offered only where they work — Orders and Contacts sync are offered only for integrations that actually support them. If you try to switch on a sync an integration doesn't offer, you see a plain message and nothing changes.
Worth knowing
- Nothing to do today. Every existing connection keeps exactly the settings it had, and nothing needs reconnecting because of this update.
- It clears by itself. The card goes back to normal as soon as the integration reports that it is working again.
- Teammates who can't see full phone numbers don't see the other service's raw error text on a card — just the plain explanation.