Server errors and busy models

Errors in the 500 range mean something went wrong on Syntic’s side or between Syntic and the model, not in your request. They are usually brief. Retry after a short wait, and if they continue, check status.syntic.ai.

Codes you may see

Status	Code	Message	Meaning
500	internal_error	”An internal error occurred. Retry shortly; contact support with the request id if it persists.”	An unexpected failure inside Syntic.
500	server_misconfigured	”The service is temporarily unavailable. Retry shortly.”	Usually during a deployment.
502	upstream_error	”The model service returned an error. Retry shortly.”	The model failed the request.
502	upstream_unavailable	”The model service could not be reached. Retry shortly.”	A network problem between Syntic and the model.
503	service_unavailable	”The service is temporarily unavailable. Retry shortly.”	A short outage.
503	capacity_busy	”The model is very busy right now. Nothing was charged. Retry shortly.”	The whole service is at capacity.
503	usage_check_unavailable, authorization_unavailable, plan_check_unavailable	Short messages asking you to retry	A check before your request could not run. See Usage can’t be verified.

Timeouts (408, 504) have their own page: Requests time out.

What to do

1. Retry with growing waits. For example 1, 2, then 4 seconds, with a little randomness. If a Retry-After header is present, wait at least that long. Stop after a few attempts.
2. Check the status page. If status.syntic.ai lists an incident, it is being worked on and updates appear there.
3. Simplify a request that always fails. If the same request fails every time with upstream_error, try fewer tools or a shorter prompt to find what triggers it, and report it.
4. Switch model. If one model is busy, another may answer.

In the apps

App	What you see	What to do
Web app	Due to unexpected capacity constraints, Amara is unable to respond to your message. Please try again soon.	Wait a little and send again.
Syntic Code	”The service stayed busy (overloaded or rate-limiting) through several retries. Wait a minute and send again, or pick another model with /model.”	Wait, or switch model. A backup model can be set with "fallbackModel" in your settings.
Syntic Desktop	”Service busy, try again”	Wait a moment and try again.

Reporting a server error

If an error keeps coming back and there is no incident on the status page, contact support with:

• the x-syntic-request-id response header (or request_id in the error body);
• the time of the request, with your time zone;
• the model and the error code.

Related

• Too many requests (429)
• Check Syntic’s service status