Performance, Webhooks & Network Errors

1. Webhook Failures for Marketplace Apps

Marketplace apps that rely on webhooks (e.g., Slack or Microsoft Teams notifications) stop sending updates.

Resolution

  1. Check the Webhook Logs in the Stack settings for failed delivery attempts.
  2. Verify that the app's target endpoint is not blocking Contentstack's IP addresses.
  3. Ensure the webhook status is set to "Enabled".

Trigger a test event (like an entry publish) and check if the app receives the notification.


2. App Dashboard Slow Performance (High Latency)

Marketplace apps take a long time (up to 3 minutes) to load their dashboards.

Resolution

  1. Check the size of the data being requested; minimize deep reference nesting in the app's initial fetch.
  2. Verify the status of the app's external hosting provider (e.g., AWS, Vercel).
  3. Implement caching on the app's backend to reduce frequent API calls.

The app dashboard loads in under 5 seconds on subsequent refreshes.


3. "Bad Gateway" (502) Errors on Public App UI

A public app displays a "502 Bad Gateway" error instead of its dashboard.

Resolution

  1. This usually indicates the app's hosting server (outside of Contentstack) is down or crashing.
  2. Check the server logs for the app's hosting environment for memory or timeout errors.
  3. Ensure the server is capable of handling the current volume of requests.

The app UI loads after the hosting server is restarted or scaled.


4. Marketplace App Assets Not Loading (HTTPS/SSL)

Images or styles within a Marketplace app fail to load, with browser errors regarding "Mixed Content".

Resolution

  1. All assets used by the app must be served over HTTPS.
  2. Verify that the hosting server has a valid SSL certificate.
  3. Check for hardcoded http:// links in the app's source code and update them to https://.

All app assets load without security warnings in the browser.


5. Retrieving full entry data in translation webhook payloads

Receiving webhook notifications for translation events may result in missing translatable fields when payload settings are restricted. This prevents external systems from accessing the full entry content required for translation.

Root cause

The "Concise Payload" configuration option is enabled, which limits the webhook response to a minimal set of metadata instead of the full entry body.

Resolution

  1. Navigate to the Webhook configuration page in the stack settings.
  2. Locate the specific webhook used for the translation workflow.
  3. Uncheck the "Concise Payload" checkbox to allow the transmission of the full entry details.

After disabling the concise payload option, trigger a translation event and inspect the webhook logs.

If the payload contains the full set of translatable fields, the configuration update is successful.