"Error occurred when trying to refresh process token" (AADSTS700082) – Welcome! How can we help?

This article explains the warning "Error occurred when trying to refresh process token" on the WorkPoint Administration dashboard, why it shows up, and how to fix it.

❓ What does this warning mean?

Every night, WorkPoint 365 tries to refresh the token for the WorkPoint Automate connection. This warning means those refresh attempts have been failing. After 90 days without a successful refresh, Microsoft Entra ID invalidates the refresh token, and WorkPoint shows the warning on the dashboard.

The message typically contains:

AADSTS700082: The refresh token has expired due to inactivity.
... was inactive for 90.00:00:00.

⚠️ Is this only an informational message?

No. The connection used to run WorkPoint Automate processes is no longer authenticated. Automate processes and steps that use this connection may fail until it is re-authorized.

🔍 Why did the nightly refresh stop working?

The usual cause is a change to the service account registered under Automate → Connections, for example:

The password was reset or has expired
MFA or Conditional Access policies were changed
The account was disabled, deleted or renamed
Consent or delegated permissions were revoked
The account is no longer a Site Collection Administrator on the WorkPoint solution

🛠️ How do I fix it?

Open WorkPoint Administration.
Go to Automate → Connections.
Under Connection for WorkPoint Automate steps, check which account is registered.
Click here to re-authorize, and sign in with the service account.
Make sure the account is a Site Collection Administrator on the WorkPoint solution.

💡 Tip: If you switch to another account, make sure it isn't blocked by MFA or Conditional Access policies that prevent it from refreshing tokens without user interaction.

⏳ I've re-authorized, but the warning is still there

The banner is only updated after the next nightly refresh. Wait 24 hours. If the refresh succeeds, the warning disappears by itself.

🔁 The warning came back after 24 hours

The nightly refresh is still failing. Check the account again for sign-in blocks, Conditional Access policies or missing permissions. If you can't find the cause, contact WorkPoint Support and include:

The solution URL
The account registered under Automate → Connections
A short description of recent changes to that account
Whether other Automate processes on the solution are failing
A screenshot of the warning, including Trace ID, Correlation ID and timestamp

✅ How do I prevent it from happening again?

Use a dedicated service account for the Automate connection, with a password that doesn't expire.
Exclude the account from interactive MFA and Conditional Access policies, or configure them so token refresh isn't blocked.
Agree internally that changes to this account must always be followed by re-authorizing the connection in WorkPoint.
Use the accounts description field to describe what the account is used for.