## TL;DR

With @propelauth/react, the auth token was not being auto-refreshed: a user who left a page open for about 30 minutes and came back hit an error page because the token had expired.

## Steps

1. With @propelauth/react, the auth token was not being auto-refreshed: a user who left a page open for about 30 minutes and came back hit an error page because the token had expired. The client's periodic refresh was not firing as expected. Users only noticed when they returned to a long-idle tab and every authenticated action failed at once.

2. PropelAuth shipped a fix for the token refresh; upgrade @propelauth/react to the release from late November 2023 or newer and the periodic refresh works. The reporter confirmed the upgrade resolved it. The fix went out the weekend the issue was reported, so any @propelauth/react version installed after late November 2023 includes it.

## When to use

You are seeing this: The client's periodic refresh was not firing as expected. Use this skill when you run into "Auth token not auto-refreshed with @propelauth/react (stale after ~30 min)".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

With @propelauth/react, the auth token was not being auto-refreshed: a user who left a page open for about 30 minutes and came back hit an error page because the token had expired.
