On Executor Cloud (executor.sh), no connection can be created in my organization. Every credential write fails, both API-key connections and OAuth.
In the web UI (GitHub OAuth via Add account):
Connection failed: Could not complete authentication
Failed to mint OAuth connection: WorkOS Vault secret write failed
Via the API (POST /api/connections with a personal API key), every attempt returns {"_tag":"InternalError"}. The failures cover owner user and org, the github_com_openapi and cloudflare_com integrations, and the templates "" and apikey-1. I also tried an obviously fake credential value, which gives the same result.
Trace IDs (2026-09-26, roughly 19:30–19:52 UTC):
057730b8e9804d57a8a9ff00acb7cda10bde3b0f07d74cfe9139eaf56733121efc7da12bf51441b7b93927e040040180e5af08f26f544e65bfe36da9e855437457262e81afa44a2a907eaf5ef94726549f0bc5d27fc348d290f031e7547357ad
The same API key works for other writes: PUT /api/integrations/{slug}/health-check succeeds, and POST /api/connections/validate returns healthy for the same GitHub token. The problem seems specific to the WorkOS Vault createObject path. The org is newly created and has never had a connection, so this could be the first KEK provision for the org's context failing. /api/providers returns only ["workos-vault"], so there is no fallback.
Repro: new Cloud account → add the GitHub REST OpenAPI integration → Add account (OAuth, or paste a token) → the save fails.
On Executor Cloud (executor.sh), no connection can be created in my organization. Every credential write fails, both API-key connections and OAuth.
In the web UI (GitHub OAuth via Add account):
Via the API (
POST /api/connectionswith a personal API key), every attempt returns{"_tag":"InternalError"}. The failures cover owneruserandorg, thegithub_com_openapiandcloudflare_comintegrations, and the templates""andapikey-1. I also tried an obviously fake credential value, which gives the same result.Trace IDs (2026-09-26, roughly 19:30–19:52 UTC):
057730b8e9804d57a8a9ff00acb7cda10bde3b0f07d74cfe9139eaf56733121efc7da12bf51441b7b93927e040040180e5af08f26f544e65bfe36da9e855437457262e81afa44a2a907eaf5ef94726549f0bc5d27fc348d290f031e7547357adThe same API key works for other writes:
PUT /api/integrations/{slug}/health-checksucceeds, andPOST /api/connections/validatereturnshealthyfor the same GitHub token. The problem seems specific to the WorkOS VaultcreateObjectpath. The org is newly created and has never had a connection, so this could be the first KEK provision for the org's context failing./api/providersreturns only["workos-vault"], so there is no fallback.Repro: new Cloud account → add the GitHub REST OpenAPI integration → Add account (OAuth, or paste a token) → the save fails.