App builder Internal Server Error | Community
Skip to main content
P
Pablo_ArielGo
August 5, 2025
Question

App builder Internal Server Error

  • August 5, 2025
  • 2 replies
  • 3125 views

Hi, 

 

I started to faced this issues without any change from code : 

1. Service getProjectById failed. Error code: 500 , Error message: Internal Server Error

2. Start creating registrations for the provider: Commerce Provider - appconnect-qa

An error occurred:
 
REGISTRATIONS_ONBOARDING → CREATE_EVENT_REGISTRATION_FAILED  
 
Process of on-boarding (registrations) failed:
I/O Management API: call to https://api.adobe.io/events/1215949/4566206088345480015/4566206088345506561/registrations returned a non-2XX status code  
Additional error details: {
 code: 500,
 entityName: 'product',
 provider: {
   id: 'f0511b4a-d8de-40de-a1b4-1ac67bc89546',
   instanceId: '338050cb-638a-407c-872c-5807c84de325',
   key: 'commerce',
   label: 'Commerce Provider - appconnect-qa'
 },
 response: {
   message: 'Unexpected response from upstream http service (url: https://api.adobe.io/runtime/namespaces/1215949-appconnect-qa/actions/sync_event_handler_Xqzp0wDco5, requestId: w0KycFftYaVigClKSGCWKNe6fvPFZpm
h). Please take a note of the http response `x-request-id` header for debugging/support.',
   reason: 'Adobe I/O Events Runtime Error. Request id: yALIEztdu5peWcGoMmXEZfGZwF5hQ1q6.'
 }
}

2 replies

M
ManikandanMo
September 27, 2025

Is this got fixed? I'm also facing the same error.

AmitVishwakarma
Community Advisor
AmitVishwakarmaCommunity Advisor
Community Advisor
March 5, 2026

Hi ​@ManikandanMo and ​@Pablo_ArielGo 

That 500 during onboarding:
Unexpected response from upstream http service (url: https://api.adobe.io/runtime/.../actions/sync_event_handler_..., ... Adobe I/O Events Runtime Error)

means I/O Events is trying to create a registration that points to a Runtime action which does not exist or is not deployed correctly in that namespace. This is a known pattern for npm run onboard / App Builder Commerce providers.

 

Fix – short checklist

  1. Verify Runtime actions exist in the namespace shown in the error (e.g. 1215949-appconnect-qa):
    • In Developer Console -> your project/workspace -> Runtime, confirm the consumer action(s) referenced in app.config.yaml are listed and “Deployed”.
  2. Deploy the app before onboarding:
    • Run aio app deploy (or the project’s npm run deploy) and ensure it finishes without errors.
  3. Re-run onboarding/registrations:
    • Run npm run onboard again. It should now create the registrations without the 500.

The initial Service getProjectById failed. Error code: 500 is usually a transient Console/back-end issue; it typically disappears once the project is correctly deployed and onboarding is retried.

Amit Vishwakarma - Adobe Commerce Champion 2025 | 16x Adobe certified | 4x Adobe SME
Terms & ConditionsAccessibility statement

Loading footer...