Reconnecting an app that stopped working Guide

Connections to your tools can occasionally stop working, most often because a sign-in session expired, you changed your account password, or access was revoked on the provider's side. When this happens, your assistant and agents can no longer act in that app until you reconnect. This guide walks you through restoring the connection.

Signs an app needs reconnecting

You'll usually notice one of these before you go looking:

• Your assistant tells you it couldn't complete an action in a connected app, or that it lost access.
• An agent that relies on the app stops running its tasks as expected.
• On the Integrations page, the app no longer shows as fully connected, or prompts you to reconnect.

Common reasons a connection drops

• An expired session. Some providers require you to periodically re-authorize access. When that window passes, the assistant loses permission until you sign in again.
• A password change. Changing your password with the provider (or your IT team resetting it) can invalidate the existing connection.
• Revoked access. If you or an administrator removed Praxivara's access from the provider's own security or connected-apps settings, the connection stops working.
• Updated credentials. For apps you connected with an API key or credentials, rotating or replacing that key ends the current connection.

How to reconnect an app

1. Open the Integrations page from your workspace.
2. Search for the app by name, or filter by its category, and open its card.
3. Choose the option to reconnect. The flow matches how the app connects:
   • Sign-in apps (such as Google or Microsoft apps, or Slack) open a secure sign-in and consent window. Sign in with the same account and approve the requested permissions.
   • Hosted-connect apps (many CRMs, accounting, e-commerce, and scheduling tools) open a hosted window where you re-authorize access.
   • Key-based apps ask you to paste a fresh API key or credentials.
   • Apple Calendar asks for your iCloud email and an app-specific password.
4. Complete the provider's screen, then return to the Integrations page and confirm the app shows as connected again.

Tip: Reconnect with the same account you originally used. Signing in with a different account can create a second connection rather than restoring the one your agents already rely on.

If reconnecting fails

The connection window expired

If you see a message that the connection link expired, simply start the reconnect again and complete the provider's screen promptly without leaving it open.

The wrong account signed in

If the provider rejected the connection or you notice the wrong account, sign out of that account with the provider in your browser, then start the reconnect and choose the correct account.

Your key or credentials weren't accepted

For key-based apps, generate a new key or confirm the credentials in the provider's own dashboard, then paste the current values. Copy the full value with no extra spaces.

Apple Calendar won't connect

Apple Calendar requires an app-specific password generated in your Apple account, not your normal iCloud password. Create a new app-specific password and use that.

The popup was blocked

If nothing opened when you started the reconnect, allow popups for Praxivara in your browser and try again.

After you reconnect

Once the app shows as connected, your assistant and agents can use it again right away. Take a moment to confirm the actions you rely on are still enabled for the connection. If your assistant mentions that a specific action isn't turned on, open Manage actions for that app and enable it. Your selected actions and any triggers you set up are preserved when you reconnect the same account, so agents resume on their own.