Reconnecting a connection that stopped working

A service can stop accepting a connection: a password changed, a key was replaced, access was withdrawn, or a sign-in ran out. Reconnecting gives the same connection a fresh sign-in or credential. It stays the same connection, so every workflow that uses it carries on without changes.

Who can do this

Workspace Admins and Editors. Viewers see the status but not Reconnect.

How you find out

• The connection's status on Connections reads Needs reconnecting, Revoked or Expired ….
• A notification in the bell, marked as needing you:
  • "Consulace Outlook needs reconnecting" — "Microsoft 365 no longer accepts it. Workflows in Consulace that use it fail until someone signs in again." Sent to the workspace's Admins and Editors when a sign-in cannot be renewed.
  • "Consulace Outlook stopped working" or "… stops working on 3 October" — sent to the workspace's Admins when a date runs out. See Setting an expiry date for a key or password.
  • "Asha Raghunathan revoked Consulace Outlook" — sent to the workspace's other Admins and Editors.
• A run fails at the step that uses it, with a reason such as "“Consulace Outlook” is no longer working. Reconnect it on Connections."
• In the designer, the step's Connection list shows it as "Consulace Outlook — not working", with "This connection no longer works. Reconnect it on Connections, or choose another."

Steps

1. Select Connections in the bar at the top, or Reconnect on the notification.
2. Select the connection. Its panel opens on the right.
3. Select Reconnect. (Before a date runs out, the same button reads Replace key or Replace password.) The window Reconnect Consulace Outlook opens.
4. Follow the part for your kind of connection:
   • A sign-in (Microsoft 365, Google Workspace).
     1. Read the list, if there is one: "Bizomate asks Microsoft only for what your steps use. Microsoft will ask you to allow:", each permission marked New with the steps that need it, or Already allowed.
     2. Select Continue to Microsoft (or Sign in with Microsoft 365 when there is no list). The service's own window opens.
     3. Sign in as the same account and allow what is asked. Signing in as someone else connects their account instead.
   • A database. Fill in Server, Database, User and Password again — none is kept from before. Leave Test the connection before saving ticked.
   • An API key (OpenAI, Anthropic, Google Gemini). Paste the new key in API key.
   • An API key for HTTP Request. Paste the new key in Key, and check Send it as.
   • A HubSpot private app token. Paste the new token in Private app token. The field shows the ending of the one it replaces. Leave Test the connection before saving ticked.
5. Select Reconnect (or the sign-in button).

You come back to Connections with the toast "Reconnected" — "Workflows that use “Consulace Outlook” carry on from their next run."

What happens next

• The status returns to Active.
• The "needs reconnecting" and "stops working" notifications for it clear, for everyone.
• Workflows that use it carry on from their next run. Runs that already failed stay failed; select Run again on a run to repeat it.
• While you sign in again, workflows using the connection keep running on what it had.

Good to know

• A revoked connection can be reconnected the same way. Until then it holds no credential at all.
• A test before saving means a mistyped key or password never replaces one that works: if the service refuses it, nothing is changed.
• From a step that needs more permission, its own Reconnect opens this window directly and brings you back to the designer afterwards. See Allowing a step more permissions.
• If the connection is no longer needed, delete it instead: an expired, revoked or "needs reconnecting" connection shows Delete beside Reconnect.

If something goes wrong

Related

• Testing a connection
• Allowing a step more permissions
• Setting an expiry date for a key or password
• Revoking or deleting a connection
• Reading a run: steps, inputs and outputs