App Management API returns 404 "Cannot find a valid organization" for newly created org - CLI fully blocked #8753

Activity

1. boainet commented on Oct 5, 2026

   

   boainet

   on Oct 5, 2026

   Last edited by boainet

   Author

   More actions

   Deeper diagnosis (direct API probing with the CLI's own session token, read-only):

   The failure is NOT app-specific - the App Management gateway cannot establish ANY organization context for this identity, while the BusinessPlatform side sees it fine.

   Evidence:

   1. Auth is healthy: CLI session token valid, and the CLI's cached BusinessPlatform response (destinations.shopifysvc.com UserInfo query) returns:

   {"currentUserAccount": {"uuid": "62e14714-e8c9-48bb-8ed6-22be0a3a4024", "email": "[email protected]",
     "organizations": {"nodes": [{"name": "Oujiang AI Information Services"}]}}}

   So the identity→organization link exists on the BusinessPlatform side, and the CLI is logged into the same account that owns the dashboard.

   2. App Management (app.shopify.com/app_management/unstable/graphql.json) rejects everything, even org-agnostic queries - with Authorization: Bearer <identity token>:

   query { appByKey(key: "bd8fb...") { id } }        -> HTTP 404 {"errors":"Cannot find a valid organization"}
   query { apps(first: 5) { nodes { id } } }          -> HTTP 404 {"errors":"Cannot find a valid organization"}
   

   An apps list query does not reference any specific app or org, yet it still 404s - the gateway fails while resolving the caller's organization context, before query execution.

   3. New request IDs from today's runs: 01a10b3e-505b-726b-a004-3772f5564b72-1791189995, 01a10ab1-e08c-7faa-80b7-c9722543f172-1791180791.

   Conclusion: the organization "Oujiang AI Information Services" (dev.shopify.com org 239033978 / Partner org 5231408) is visible to the BusinessPlatform but absent from the App Management authorization layer's organization index for user 62e14714-e8c9-48bb-8ed6-22be0a3a4024. Both appByKey and org-independent queries fail identically.

   Specific ask: check the App Management org-index wiring for this user/org pair - likely provisioning between the new Dev Dashboard backend and the App Management service was not completed for orgs created there. Happy to run any specific probe that helps.
2. boainet commented on Oct 6, 2026

   

   boainet

   on Oct 6, 2026

   Author

   More actions

   Control experiment result (2026-10-06): not platform-wide — org-scoped provisioning failure.

   We ran an A/B probe within the same minute, using the same CLI session token (atkn_2 opaque token), same account:

   Target	shopify app config link result
   Brand-new Partner org created 2026-10-06 (5234196), brand-new app (manual creation in Dev Dashboard, client c7a411cbba67d320451e38f5cd1c6424)	✅ success — config linked, and app deploy released version mothertalk-live-translate-2 (theme extension uploaded fine)
   Original org (5231408, App Store registration completed), original app (client bd8fb17b98cbe5db668095c63e8a602d)	❌ HTTP 404 "Cannot find a valid organization" — Request ID 01a10f1a-8710-72d9-b43c-87eab52f9fea-1791254759
   Original org 5231408, brand-new app created 2026-10-06 (client 5c1c4d291f35f70bf7a2a4ca9087f7e96)	❌ same 404 — Request ID 01a10f21-4bff-7f45-9b4b-ba8a571e9e8a-1791255202

   Conclusions:

   • The CLI, token and Dev Dashboard flow all work for a newly created org — so this is not a general new-org provisioning regression.
   • A brand-new app record created today inside the original org still 404s, so it is app-record-independent.
   • This narrows the fault to the organization object 5231408 itself in the App Management authorization/index layer (matches the earlier finding that destinations recognizes the org but app_management 404s everything).

   Earlier failed Request IDs from 2026-10-05/06 on org 5231408: c1dd9f6b-64eb-4be7-9c59-6d707fee529e-1791251877 (plus three others already shared with support).

   We have a support ticket open with Shopify Partner Support asking them to repair the provisioning data for org 5231408. Work continues on org 5234196 in the meantime.