Solution skill
Box refresh tokens expire after 14 days by design
Complete solution
If you integrate with the Box API, design for the 14-day refresh token lifetime from the start: refresh on a schedule well inside the window, or lazily refresh before expiry on every run, and treat a 400 on refresh as a signal to re-run the full authorization flow, not as a transient error to retry.
Box refresh tokens expire after 14 days by design
TL;DR
If you integrate with the Box API, design for the 14-day refresh token lifetime from the start: refresh on a schedule well inside the window, or lazily refresh before expiry on every run, and treat a 400 on refresh as a signal to re-run the full authorization flow, not as a transient error to retry. Context: Stack Overflow #15564486 (accepted answer, 14 votes): the asker wanted to know why every Box refresh token dies after 14 days. The top-voted answer (14 votes) is from the Box team: the 14-day lifetime is deliberate OAuth2 security policy, chosen from developer feedback and login-frequency data showing most users sign in more often than that.
Use this when you run into the situation in the title.
When not to use this skill: unrelated tasks. It covers only the procedure above.
Compatibility
The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.
Details
There is no configuration to extend it; the refresh token simply has to be used at least once every 14 days to stay alive.
Evidence
Source: Stack Overflow #15564486 (accepted answer, 14 votes): the asker wanted to know why every Box refresh token dies after 14 days. The top-voted answer (14 votes) is from the Box team: the 14-day lifetime is deliberate OAuth2 security policy, chosen from developer feedback and login-frequency data showing most users sign in more often than that. There is no configuration to extend it; the refresh token simply has to be used at least once every 14 days to stay alive.
Verified resolution: If you integrate with the Box API, design for the 14-day refresh token lifetime from the start: refresh on a schedule well inside the window, or lazily refresh before expiry on every run, and treat a 400 on refresh as a signal to re-run the full authorization flow, not as a transient error to retry.
Source URL: https://stackoverflow.com/questions/15564486/why-do-refresh-tokens-expire-after-14-days
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_YZORy0EOCgcZEyHLZqCusA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Box refresh tokens expire after 14 days by design <span>— Vectle</span></a>