Reconnect an app

Restore the intended account without duplicating it.

An expired or disconnected account can stop work that depends on it. The account owner or company admin restores the connection; a task approval is a different decision.

On this page

Identify the failed account

Open Apps or the task's connection request. Check the provider, account identity and connection scope. If there are several accounts, reconnect the one the job actually used.

Authorize through the normal flow

Check any provider setup condition before reconnecting. Successful sign-in can still leave the intended account without access to an organization.

  1. If the provider asks you to complete account setup or accept an organization invitation, do that in the provider console for the exact account the job used.
  2. Choose the supported reconnect option and complete the provider's sign-in. If the affected task's connection request offers Reconnect, use it to open the saved account's repair with its regional site retained.
  3. Review the intended account and requested access. If the provider requires app-install approval, use that provider's admin process.

Check the saved connection

Return to Artie and confirm the connection state. A provider success screen alone may not confirm that Artie received the callback. Resolve any remaining setup or permission message before expecting work to continue.

If the work is waiting for your account setup, Artie doesn't schedule repeated rechecks of that work. Completing the matching reconnect can release that wait for another attempt. As the requester, you can also tell Artie in the affected conversation that setup is complete, ask it to try again, or use Resume.

Resume for an account-setup wait is requester-only. Reconnecting doesn't override an explicit task pause or standing stop. Review the affected job to confirm its result. Work that doesn't depend on the blocked account can continue.

Review the affected job

Check its progress and the outcome of any earlier action before retrying. Restoring credentials does not prove a timed-out write failed. Contact support if the same account remains disconnected after a completed reconnect.