PerfectMileMCP OAuth — LPH scope not restoring after re-auth

Q&A
,
1

My PerfectMileMCP connection in Amazon Quick is partially broken. After the OAuth token expired, I’ve tried the following to restore it:

  • Toggled the connection off/on (multiple times)

  • Full app restart + re-toggle

  • Complete sign-out and sign-in to Amazon Quick

Current state:

  • :white_check_mark: Goodman API calls work (namespace list, metric metadata) — auth is valid for this service

  • :cross_mark: LPH API calls all return HTTP 403 — Missing Authentication Token — this includes both lph_get_metric_tool and lph_get_metric_data_tool

This suggests the OAuth grant was re-issued with only partial scopes (Goodman but not LPH). I cannot find a way to fully remove and re-add the connection in the UI — only a toggle is available.

Impact: My scheduled productivity watchdog (pulls NonSort Productivity DRB, USNS DBR, USNS CX STL, qubit_ship_ship_dock_uph for SMF6) has been failing since at least June 8. Prior error events: evt_00422, evt_00445, evt_00449.

Request: Please revoke and re-issue the full OAuth grant for my PerfectMileMCP connection (alias: chriszro,

2

Hi @chriszro and welcome to the Quick Community!
Please note that the Community is more of a public facing forum as opposed to an area to request internal support. We would be unable to assist with private account/internal organization matters as we would not have proper permissions or access.
I would suggest reaching out through an internal channel to get support in relation to this issue!