[REOPENED] - POST /api/latest/fleet/trigger?name=cleanups_then_aggregation comes back with 401 status (Unauthorized)

[qa-wolf]

Steps to reproduce:

1. Log in as fleet+GlobalAdmin3@qawolf.email (https://mailto:fleet+GlobalAdmin3@qawolf.email)
2. Navigate to Ducks team
3. Make an API call to:https://qawolf-premium.cloud.fleetdm.com/api/latest/fleet/trigger?name=cleanups_then_aggregation
4. Observe status
   Expected: Status should return as 200
   Actual: Getting a 401 response
   Response {
   status: 401,
   statusText: 'Unauthorized',
   headers: Headers { date: 'Fri, 09 May 2025 16:09:10 GMT', 'content-type': 'text/plain; charset=utf-8', 'content-length': '188', connection: 'keep-alive' },
   body: ReadableStream { locked: false, state: 'errored', supportsBYOB: true },
   bodyUsed: false,
   ok: false,
   redirected: false,
   type: 'basic',
   url: 'https://qawolf-premium.cloud.fleetdm.com/api/latest/fleet/trigger?name=cleanups_then_aggregation (https://qawolf-premium.cloud.fleetdm.com/api/latest/fleet/trigger?name=cleanups_then_aggregation)' }
   Video:
   https://www.loom.com/share/5db5918907c24e05a9e979a0069b53a9 (https://www.loom.com/share/5db5918907c24e05a9e979a0069b53a9)

[lucasmrod]

I was not able to reproduce (using a global admin on https://qawolf-premium.cloud.fleetdm.com).

I successfully ran

fleetctl trigger --context qa-wolf --name cleanups_then_aggregation
[+] Sent request to trigger cleanups_then_aggregation schedule

It's possible the API token used by the user expired or is not valid anymore.

[juan-fdz-hawa]

I couldn't replicate this either in my local env :

As pointed out by @lucasmrod - my money is on that the API call was made just after the token expired (hence the 401 status code), closing this.

[fleet-release]

Unauthorized, a wall,
Fix brings status two hundred,
Glass city unblocked.

[fleet-release]

API call once blocked,
Now flows like a clear spring stream,
Access granted, unlocked.