OAuth consent finished but the agent still says "Connect Microsoft"

Browser callback timed out. Re-trigger the connect flow.

Avery runs the OAuth flow with a loopback HTTP listener for the redirect URI. If your browser took longer than 2 minutes to land back on `localhost:NNNNN`, the listener gives up + the connection isn't recorded.

Steps

1. Re-open the connect popup.

   From the agent's setup task OR the global Connectors page.

   Go to Connectors →

2. Click Connect again.

   Avery starts a fresh consent flow with a new loopback port.

3. Approve quickly.

   The browser redirect is the slow part. If your default browser was sleeping, it can take a moment to wake up — that's where the previous attempt timed out.

Live recipes need the desktop

This article is a static preview. The in-app Help sidecar inside Avery NXR can fire each step against your live project — install the desktop to use it interactively.

Download desktop →