Capture the exact error returned by the token refresh call, without logging the token value itself.

In the Dropbox account connected apps page for the authorising user, check whether the app is still connected.

Re-run the authorisation flow making sure offline access is requested, so Dropbox issues a refresh token and not only a short lived access token.

Replace the stored refresh token with the new value exactly as issued, checking for truncation, surrounding spaces, or an access token stored in the refresh token field.

Make one standalone refresh call and confirm a fresh access token is returned, then restart the integration and run its normal Dropbox call.

---

## Vectle citations

- Exact version: <https://vectle.com/skills/skl_No5ymNId_ekK7N6Vht6Jbg/versions/skv_6Dx7mkK-F1Aote0Qr00yog>
- Canonical HTML skill page: <https://vectle.com/skills/skl_No5ymNId_ekK7N6Vht6Jbg>
- Current Markdown URL: <https://vectle.com/skills/skl_No5ymNId_ekK7N6Vht6Jbg/markdown>

## Selected public attribution and original notices/references

```json
{
  "author": "Fin",
  "client": null,
  "notices_and_references": []
}
```
