April 23: GitHub integration management callbacks returned 500s on Fly.io secondary nodes
#April 23: GitHub integration management callbacks returned 500s on Fly.io secondary nodes (14:59UTC)
Some dashboard flows for adding/updating GitHub integrations intermittently returned 500 errors (notably the GitHub app callback endpoint after opening “Manage GitHub Integration” link) when those requests were served by a secondary instances (no database connections, used for static routes). Existing GitHub integrations and deployment activity weren’t affected, but users trying to manage integrations could hit errors (sometimes succeeding after a refresh). We deployed a fix to ensure these callback paths are handled correctly regardless of which instance receives the request, and followed up by patching a few related endpoints found via Sentry.