Error codes — Altifigence Documentation

Public error codes that ALcad and Digital Design Studio show on screen, listed by product.

ALcad and Digital Design Studio show a public error code when they reject an export or a request. Each section below lists the public codes of one product. An entry gives a cause and an action only when they hold for every case that shows the code.

To search by code, message, product or situation, use the error code search.

ALcad

ALcad shows these codes in Export rejected when it rejects an export.

`wrong_kind`

Cause: An edit or the design uses an item of the wrong kind: a track on a layer that is not a copper layer, an edit that selects an item that is not the via, track or component it changes, or a symbol placement that would move an existing symbol to another component.

Action: In an export, this code means that the saved design has a track on a layer that is not a copper layer. Choose File → Workspace → Reload project to read the saved project again. If another program or a file sync changed the design file, put back the file that ALcad saved, reload, and start the export again. If reload fails, choose File → Workspace → Open configured project… → Choose project folder… and open the project folder again. If you cannot open it or the export fails again, contact support with the error code and message shown.

`unsupported_schema`

Cause: The project manifest (project.alcad.json) or the design file declares a format or format version that this version of ALcad does not read.

Action: Choose File → Workspace → Reload project to read the saved project again. If the project files were replaced by files from another version of ALcad or another program, put back the files that this version of ALcad saved, reload, and start the export again. If reload fails, choose File → Workspace → Open configured project… → Choose project folder… and open the restored project folder. If you cannot open it or the export fails again, contact support with the error code and message shown.

`duplicate_id`

Cause: The saved project or design uses the same ID for more than one object or file reference, or a copper zone has an ID too long for ALcad to make IDs for the zone's fill from it.

Action: Choose File → Workspace → Reload project to read the saved project again. If another program or a file sync changed the project files after ALcad saved them, put back the files that ALcad saved, reload, and start the export again. If reload fails, choose File → Workspace → Open configured project… → Choose project folder… and open the restored project folder. If you cannot open it or the export fails again, contact support with the error code and message shown.

`parse_failed`

Cause: ALcad could not read the project manifest or the design file as project data: the file is not valid JSON in the expected structure, or it is larger than ALcad reads.

`integrity_mismatch`

Cause: The saved design no longer matches the content fingerprint recorded in it, or the contract packet named in the project manifest does not match this version of ALcad. This happens, for example, when the design file was edited outside ALcad.

`invalid_path`

Cause: A project file or folder is not where or what ALcad expects. For example, a path in the project manifest is not a plain relative path inside the project folder or is listed twice, a component's 3D model is not listed in the manifest, a project file or folder is a link, or its owner or permissions are not the ones ALcad requires.

Action: Keep the project files in the project folder under the names listed in the project manifest, as regular files rather than links. On Linux, your user account must own the project folders and have read, write and execute permission on them, other users must not be able to write to them, and the project manifest and design file must have permission 0600. If the project manifest lists a path twice or does not list a component's 3D model, put back a copy of the project that ALcad saved. Then choose File → Workspace → Reload project and start the export again. If reload fails, choose File → Workspace → Open configured project… → Choose project folder… and open the project folder again. If you cannot open it or the export fails again, contact support with the error code and message shown.

`invariant_violation`

Cause: The saved design breaks a rule that every ALcad design keeps. For example, two components have the same reference, a component has two pins with the same number, or a component does not have exactly one symbol or has more than one footprint.

`invalid_reference`

Cause: The saved project or design has a reference, list or text value that ALcad does not accept. For example, a track, via or copper zone uses a missing net or layer, a symbol, pin or footprint points to a missing component, the project manifest and the design belong to different projects, a list or text is longer than ALcad allows, or the project name is empty.

`not_found`

Cause: A file or folder that the project needs is missing. For example, the project folder or the design file named in the project manifest was moved, renamed or deleted after ALcad opened the project.

Action: Put the project folder and its files back where ALcad opened them, under the names listed in the project manifest. Then choose File → Workspace → Reload project and start the export again. If reload fails, choose File → Workspace → Open configured project… → Choose project folder… and open the restored project folder. If you cannot open it or the export fails again, contact support with the error code and message shown.

`io_failed`

Cause: The operating system reported an error while ALcad opened or read the saved project files, for example because a file could not be read or the storage that holds the project was not available.

Action: Check that the storage that holds the project is connected and that your user account can read the project files. Then choose File → Workspace → Reload project and start the export again. If the code appears again, contact support with the error code and message shown.

`invalid_geometry`

Cause: A shape check or a related check failed while ALcad prepared the fabrication files. For example, a board or zone outline has too few or too many points, a via does not run between two different copper layers in stack order, or a copper zone fill exceeds its size limit.

Action: Read the message shown next to the code. Then choose File → Workspace → Reload project and start the export again. If reload fails or the code appears again, contact support with invalid_geometry and the message shown.

services

Digital Design Studio shows these codes as error text in the IDE when a Cloud workspace request is rejected.

`PRECONDITION_REQUIRED`

Cause: A required quoted version is missing or invalid. For a request that requires a file or workspace version, the value must be 64 lowercase hexadecimal characters enclosed in double quotes.

Action: Reopen the project (in a browser, you can reload the page), then repeat the action. If the code appears again, contact support with the error code shown.

`INVALID_IDEMPOTENCY_KEY`

Cause: The idempotency key is missing or does not match the required format. Requests that must take effect only once, such as submitting a job or starting or stopping a workspace, must carry this key.

Action: Reopen the project (in a browser, you can reload the page), then repeat the action. If the code appears again, contact support with the error code shown.

`INVALID_REQUEST`

Cause: The request body, fields, headers or other request details do not meet the requirements for this action.

Action: Check the names, paths and options you entered for the action, then repeat it. If the code appears again, reopen the project (in a browser, you can reload the page) and repeat the action. If it still appears, contact support with the error code shown.

`UNSUPPORTED_MEDIA_TYPE`

Cause: The request's Content-Type header is missing or is not exactly application/json.

Action: Reopen the project (in a browser, you can reload the page), then repeat the action. If the code appears again, contact support with the error code shown.

`INVALID_PATH`

Cause: A file or folder path in the request is not allowed in a Cloud workspace, or a rename would keep the file at the same path.

Action: Choose another name or path, then repeat the action. A path must not start or end with /, must be at most 256 bytes and 32 levels long, and must not contain \ or control characters. No part may be empty, . or .., end with a dot or a space, or have a reserved device name such as CON, NUL, COM1 or LPT1 before its first dot. The first part must not be a reserved folder such as .git. Source paths for an RTL schematic may use only the letters A–Z and a–z, digits, /, _, . and -.

`BODY_TOO_LARGE`

Cause: The request body exceeds the size allowed for this action, or its declared length is invalid.

Action: If this happened while you saved a file, make the file smaller, for example by splitting it into several files, and save it again. If the code still appears, or if it appears for another action, contact support with the error code shown.

`INVALID_IDENTITY`

Cause: An identifier in the request, such as a project, organization, user, job or request ID, is not in the required UUID form, or the request did not identify its Cloud workspace correctly.

Action: Reopen the project (in a browser, you can reload the page), then repeat the action. If the code appears again, contact support with the error code shown.