Errors and limits¶
Inspect the response body as well as the HTTP status. General errors use an error envelope with code/message and request identity where supplied; budget refusals and endpoint-specific responses can have their own documented shapes. MCP callers must also inspect isError and structuredContent.
Outcome |
What to do |
|---|---|
401 authentication |
Reconnect with a valid credential; do not expose it in logs |
403 permission |
Check scopes, ownership and membership; request authorised access |
404 unavailable resource |
Verify the ID and current access; do not guess another user’s IDs |
409 conflict |
Reconcile idempotency, expected revision, resource state or ownership |
413 size limit |
Use a supported bounded input/workflow; do not truncate engineering data silently |
422 validation |
Correct the exact field/type/combination indicated |
429 capacity/rate limit |
Respect the supplied retry interval; do not start replacement work |
402 budget refusal |
Present the estimate and authorised billing/budget action to the person |
5xx / network timeout |
Inspect the existing job/operation before retrying any mutation |
|
Follow the supplied approval action; changing keys/files does not create authority |
Engineering refusals¶
A plan can return feasible=false without a transport error. Examples include a requested count too small for fixed sizes, unresolved boundary-layer thickness or a memory estimate beyond capacity. Read the returned numbers and propose a change to the conflicting requirement. Do not silently loosen y+, remove layers or reduce geometry fidelity.
Job errors can identify the stage, elapsed time and whether the same request might succeed. That advice does not automatically authorise a new compute attempt. Preserve diagnostic evidence when asking for a revised decision.
Limits are operation-specific¶
Current default bounds include a 20-million-cell mesh request ceiling, a 256 MiB geometry-inspection/large-STL preparation limit, and a 1 GiB source limit for supported mesh/result viewing. Direct surface intake can accept larger files than downstream inspection. Document intake, view payloads and section complexity have separate limits.
Read the connected service’s schema and returned limits. A cell ceiling is not a memory guarantee. An accepted upload does not guarantee successful meshing, viewing or simulation. Do not split a model in a way that changes its physical meaning merely to evade a size limit.
For support, retain the request/job/operation ID, stage, timestamps and a redacted description of the problem. Never include keys or complete private capability URLs in public reports.