The application makes requests against the Edge API using the configured auth token, for a given deployment.
For any reason, this token may be incorrect/invalid, but it seems like the code will continue retrying/re-polling regardless.
We should investigate where 401s can occur, and encode an escape hatch, that kills or halts polling in the event of a 401 response. These are wasted API calls, and incur operational costs which could otherwise be avoided.
Screenshot of 89k 401s across all deployments of AEMCP within the last week:
https://magento.slack.com/archives/C080XP30Q59/p1789663113102659
The application makes requests against the Edge API using the configured auth token, for a given deployment.
For any reason, this token may be incorrect/invalid, but it seems like the code will continue retrying/re-polling regardless.
We should investigate where 401s can occur, and encode an escape hatch, that kills or halts polling in the event of a 401 response. These are wasted API calls, and incur operational costs which could otherwise be avoided.
Screenshot of 89k 401s across all deployments of AEMCP within the last week:
https://magento.slack.com/archives/C080XP30Q59/p1789663113102659