Skip to main content

Callout Errors (Service Unavailable)

If you see a "Service Unavailable" or "503" error when running a scan or accessing aprity features, the most likely cause is a backend cold start.

Why this happens​

The aprity backend runs on Azure Container Apps, which uses a scale-to-zero architecture. When the service has not been used recently, the underlying containers are deallocated to reduce costs. The first request after a period of inactivity triggers a cold start, which can take 30 to 60 seconds.

During this cold start window, requests may receive a 503 (Service Unavailable) response.

Built-in retry logic​

The aprity Salesforce app includes automatic retry logic for callout errors:

  • 3 retry attempts with 10-second intervals between each attempt.
  • Most cold-start scenarios resolve within the first or second retry.
  • You do not need to manually retry in most cases.
info

The retry indicator is visible in the app interface. If you see a "Retrying..." message, the app is handling the cold start automatically.

If the error persists​

If you still receive errors after the automatic retries complete:

  1. Wait 2-3 minutes. The backend may be performing a longer startup sequence (for example, after a deployment).
  2. Retry your action manually. Close any error dialogs and re-trigger the scan or operation.
  3. Check the aprity status page. Visit status.aprity.ai to see if there is a known outage or maintenance window.
  4. Verify your network. Ensure outbound HTTPS calls to api.aprity.ai are not blocked by your org's firewall or proxy.

When to contact support​

Contact support@aprity.ai if:

  • Errors persist for more than 5 minutes.
  • The status page shows no ongoing incidents.
  • You are experiencing errors across multiple operations (not just a single scan).

Include your Org ID and the timestamp of the failed request.