last week we enabled the graphite merge queue and it worked quite smoothly on our self hosted runners (using runs-on). Exactly a week later however we now find job failing due to issues refreshing the token associated with our graphite app. Worker logs are filled with messages such as the following:

failed to fetch workflow run: Get \"<https://api.github.com/repos/><redacted>/infra/actions/runs/<redacted>\": could not refresh installation id <redacted>'s token: received non 2xx response status \"404 Not Found\" when fetching <https://api.github.com/app/installations/><redacted>/access_tokens

There's nothing of note in the github audit log beyond a lack of events from the graphite bot and based on the UI it looks like we have all the permissions required for your app enabled. Should it be expected that your merge queue work with self-hosted runners?

Hey Kim! Graphite merge queue should work fine with self-hosted runners. MQ triggers your workflows on

gtmq_

branches and the Graphite GitHub App reads Actions status. That 404 on refreshing the app installation token looks like it's coming from runs-on's worker, not Graphite itself, which matches your runs-on note. If you can give me a link to a PR I can check our backend and get a better picture and report back. Thanks!