Two issues, possibly related:
1. App performance: Amazon Quick has become noticeably slow/laggy today, persisting after an app restart and a full computer restart.
2. PerfectMileMCPV2 connector (ID 21122aff-34a9-42ba-be9f-a08da45b2ff0) stuck unauthorized:
- Every tool call returns
auth_required; the in-chat sign-in card never renders
- Connection shows “connected” in Settings but tokens are expired
- Tried without success: toggle off/on, full connector reinstall, app cold-restart, computer restart
- De-authorizes ~weekly after inactivity (recurring since late Aug); request longer-lived/refresh token
- Reauth URL returned:
https://us-east-1.quicksight.aws.amazon.com/sn/account/amazonbi/action-connectors/21122aff-34a9-42ba-be9f-a08da45b2ff0/?signin=true
Hi @michfinl,
Welcome to the Quick Community! This is expected behavior when the connector’s OAuth refresh token has a short idle/inactivity timeout. The “connected” state in Settings just means the connection record exists (not necessarily that the token is live). When the access token expires and the refresh token has already been invalidated by the idle timeout, every tool call returns auth_required.
The reason reinstalling/restarting doesn’t help is that none of those actions trigger the OAuth redirect flow; they just recreate the same expired connection record. Also, when the in-chat sign-in card fails to render, there’s no in-app path to complete the re-auth handshake. I would just recommend to access the reauth endpoint directly in a browser, sign in there, then return to Quick and retry a call.
In regard to the recurring weekly de-auth, that’s not something configurable in Quick’s settings. Token lifetime, refresh-token rotation, and timeout policy are all set on the OAuth app registration behind the connector. Because of that, I believe a longer-lived token would need to be configured by a respective admin.
Hope this helps!
Hi @michfinl,
It’s been a while since we last heard from you, did you have any additional or follow up questions regarding your initial topic? Were you able to try out the second approach that was shared?
If we do not hear back within the next 3 business days, I’ll go ahead and mark the solution to close out/archive the topic.
Thank you!