Revoked connections now ask you to reconnect

When you revoke an app's access, change a password, or a sign-in expires, the service refuses to renew the connection. We used to recognize that refusal only when it matched wording we expected, so a refusal worded differently left the connection looking healthy while every workflow that used it failed. Now we read what the refusal means, mark the connection as needing to be reconnected, and tell its owner.

How it works

• Standard answers first. A service that says the sign-in is no longer valid in the standard OAuth way is recognized at once.
• Everything else is read. Other refusals, like Basecamp's or HubSpot's, are read for what they mean, and the connection is marked only after the service refuses it twice, a few minutes apart.
• Held when it may not be your sign-in. A refusal that points at the app rather than your sign-in, a service outage, or a refusal we can't place leaves the connection as it is. When a service starts refusing many workspaces at once, we wait an hour before disconnecting any of them.
• A renewal in progress wins. If the connection renews while we're deciding, it stays connected.
• Nothing to redo. Reconnecting brings back everything that used the connection, in place.

Also shipped

• A connection whose sign-in can't be renewed, such as a LinkedIn sign-in after 60 days, now asks to be reconnected instead of showing a generic error.