Skip to content

A connection has expired and needs reconnecting

When AIR works on your behalf in another system — your accounts package, your mailbox, your calendar — it holds a key that system gave it. Those keys do not last forever. They expire on a schedule the other system sets, and they stop working immediately if someone there changes a password, revokes access, or removes the account AIR was using.

Nothing is broken and nothing has been lost. The job stopped because it was refused at the door, which is exactly what should happen. It will pick up again once the connection is renewed.

Renew the connection

  1. Open Settings → Integrations.
  2. Find the connection named in the error. It will be marked as needing attention.
  3. Choose Reconnect and sign in to that system as you normally would.
  4. Come back to the failed job and choose Retry.

You are signing in to the other system, not to AIR. AIR never sees the password you type there — the other system hands back a fresh key and that is all AIR keeps.

If reconnecting does not fix it

"Permission denied" rather than "expired". The key is valid but does not allow what the job is trying to do. This usually means the account AIR is using lost a permission, or was moved to a more restricted role. Someone who administers that system needs to restore it; the error names the specific operation that was refused.

It expires again within days. Some systems issue short-lived access to accounts flagged as inactive or shared. Ask whoever administers it whether the account AIR uses is subject to a shorter policy than a normal user's.

You cannot see the connection in Settings. It belongs to a team you are not a member of. An org owner can see every connection.

Why the job did not simply retry

AIR does retry things that are worth retrying — a system being briefly unavailable, a rate limit, a timeout. An expired key is not one of them: every retry would be refused in exactly the same way, and a job silently retrying for hours is worse than one that stops and tells you. After three consecutive failures of this kind the job pauses itself, so it is not still trying in the background while you read this.