Tournevia Community guide · documents 0.8-dev (c0c68b4, 5 November 2026)Français
Messages and what to do
The messages Tournevia shows, what causes them and how to continue.
Messages appear in the interface language. Where the server refuses a request, it also returns a code, shown here in code style; a failed calculation shows its code under What to do next. Text in “…” stands for the records or values the message names. Rows without a code are checked by the interface itself, or are field or import-row messages. The server sometimes attaches the identifiers of the records concerned to a refusal; in Planning, the message then ends with Concerned: and their names or codes (Depot for the main depot).
1. Sign-in and accounts
| Message | Code | Cause | What to do |
|---|---|---|---|
| “Username or password is incorrect.” | LOGIN_FAILED | The pair does not match an active account. | Check both and retry. If you cannot sign in, contact your administrator. |
| “Sign-in temporarily limited. Try again later.” | LOGIN_THROTTLED | Too many failed attempts for this username within 15 minutes: 5 from your connection or 50 in total. Wrong current passwords in a password change count too. | Wait up to 15 minutes. Other users are not affected. |
| “Too many sign-in attempts from this address. Wait a minute, then try again.” | SIGNIN_RATE_LIMITED | The HTTPS proxy limits sign-in requests per address. | Wait a minute, then sign in again. |
| “Sign in to continue.” | SESSION_REQUIRED | Your session ended: 30 minutes without activity, 8 hours after sign-in, or a change to your account. | Sign in again in the Your session has expired dialog. Your open plan and unsaved route changes are kept. |
| “Refresh the page before submitting changes.” | CSRF_REQUIRED | The page no longer matches your current session. | Reload the page and repeat the change. |
| “Only an administrator can manage depot settings and users.” | ADMIN_REQUIRED | The action is reserved for administrators (depots and places, delivery numbers, address search, calculation settings, example data, users), or your account changed role meanwhile. | Ask an administrator. |
| “Choose a different username.” | USERNAME_UNAVAILABLE | Usernames are unique in the installation, regardless of case. | Choose another username. |
| “Usernames start with a letter or digit and use only letters, digits and . _ @ + -” | — | The username has another character or starts with a symbol. | Correct the username. |
| “Keep at least one active administrator in this company.” | LAST_ADMIN | The change would leave no active administrator. | Make another user an administrator first. |
| “Another administrator must disable or demote your account.” | SELF_LOCKOUT | You tried to disable your own account or remove your own administrator role. | Ask another administrator. |
| “Your current password is incorrect.” | PASSWORD_INCORRECT | The current password entered under Change password is wrong. | Retry with the right password. Repeated failures limit sign-in. |
| “Choose a new password different from the current one.” | PASSWORD_UNCHANGED | The new password equals the current one. | Choose a different password of at least 15 characters. |
| “The new password and its confirmation are different.” | — | The two new-password fields differ. | Type the same password in both. |
| “Change your own password from Personal preferences.” | OWN_PASSWORD | An administrator tried to set their own password from Edit user. | Use Settings → Personal preferences → Change password. |
| “Use the private setup link supplied by your installation operator.” | SETUP_UNAUTHORIZED | First-use setup was opened without a valid setup link or code. | Ask the operator for the private link. |
| “This installation is already configured. Sign in instead.” | SETUP_COMPLETE | The company and its first administrator already exist. | Sign in with your account. |
| “Company and administrator names cannot be blank.” | — | During first-use setup, one of these names contains only spaces. | Enter both names. |
| “Provide and review your depot location before creating the workspace.” | — | During first-use setup, the depot entrance is missing or was not confirmed. | Place the pin on the vehicle entrance and tick its review. |
| “Workspace setup is incomplete.” | ORGANIZATION_MISSING | Your account’s company is not fully set up yet. | Contact the installation operator. |
| “Named accounts are unavailable in legacy unauthenticated demo mode.” | DEMO_MODE | The installation runs the old local demonstration mode without accounts. | Ask the operator to use a local or shared installation. |
2. Deliveries, vehicles and customers
| Message | Code | Cause | What to do |
|---|---|---|---|
| “That identifier already exists. Edit its current version explicitly.” | IDENTIFIER_CONFLICT | Another delivery, vehicle, customer, depot or place of the company has this identifier or code. | Open the existing record, or choose another identifier. |
| “This record changed. Reload it before applying your edits.” | SOURCE_CHANGED | Someone saved the record after you opened it, or a selected delivery changed before you cancelled or deleted it. | Reload the record, then apply your change again. |
| “Record not found in this organization.” | NOT_FOUND | The record was removed, or belongs to another company. | Reload the list. |
| “Correct the highlighted fields. Your edits remain here.” | — | Fields are missing, out of range or too long. Each field states its rule, for example “Use a value of at most 10.” | Correct each highlighted field and save again. |
| “Equipment codes start with a capital letter and use only A–Z, 0–9 and _: …” | — | The named code does not follow the equipment code rule. | Correct the code; see CSV formats. |
| “Automatic delivery numbers are not set up. Enter an identifier.” | NUMBERING_OFF | The delivery number format was removed while you were adding a delivery. | Enter an identifier, or ask an administrator to set Settings › Delivery numbers. |
| “No saved customer has this code.” | CUSTOMER_UNKNOWN | The delivery names a customer that does not exist, or no longer does. | Choose a saved customer in Customer, or leave it empty. |
| “No depot or place has this code.” | PLACE_UNKNOWN | Starts at, Ends at or Ships from names an unknown code. | Choose an existing depot or place. |
| “A delivery ships from a depot, not from another place.” | NOT_A_DEPOT | Ships from names a place, such as a driver’s home. | Choose a depot, or Any depot. |
| “Only example vehicles and deliveries use an example depot.” | EXAMPLE_PLACE | One of your vehicles or deliveries names the example depot. | Choose one of your depots or places. |
| “Working hours must end after they start on the same day; overnight work is unsupported.” | — | Weekly hours or the hours of a particular date end before they start. | Correct the hours: the end follows the start, on the same day. |
| “Each date can have only one exception.” | — | Days off and other hours has two rows for the same date. | Keep one row per date. |
| “A calculation that uses these deliveries is waiting or running. Wait for it to finish or cancel it, then try again.” | JOB_ACTIVE | You are deleting deliveries that a waiting or running calculation uses. | Wait for the calculation or cancel it in Planning, then delete them. |
| “Select each delivery once.” | DUPLICATE_RECORD | A script sent the same delivery twice in one cancellation or deletion. | Send each delivery once. |
| “Set the depot and delivery coordinates before checking road access.” | LOCATION_MISSING | Check road access needs both points. | Save the coordinates first. |
| “Road check failed: correct off-road pins or check local graph/service availability. …” | ACCESS_CHECK_FAILED | No road was found near a pin, or the routing service did not answer. | Move the pin to the vehicle entrance, or ask the operator to check the routing service. |
| “Address lookup is not turned on for this workspace.” | GEOCODER_DISABLED | The installation has no address service and IGN’s service has not been turned on. | Place the pin on the map or enter the coordinates; an administrator can turn on IGN’s service in Settings › Address search. |
| “Address lookup is unavailable. Enter the coordinates or place the pin on the map.” | GEOCODER_UNAVAILABLE | The address service did not answer. | Enter the coordinates or place the pin; if it lasts, ask the operator to check the service. |
| “Address search is unavailable right now. Place the pin on the map instead.” | — | The same failure, reported under an address field. | Place the pin on the map, or try again later. |
| “No address found. Place the pin on the map instead.” | — | The lookup found nothing for the text typed. | Check the address, or place the pin on the vehicle entrance. |
3. Depots, places and example data
| Message | Code | Cause | What to do |
|---|---|---|---|
| “Depot changed. Reload before editing.” | SOURCE_CHANGED | The depot or place was saved by someone else meanwhile. | Reload it, then edit it again. |
| “Depot not found in this organization.” | NOT_FOUND | The depot or place was deleted. | Reload Depots and places. |
| “Vehicles or deliveries name this depot or place. Choose another for them first.” | DEPOT_IN_USE | You are deleting a depot or place, or changing its code, while vehicles or deliveries name it. | Give them another depot or place, then try again. Saved plans keep their own copy. |
| “Deliveries ship from this depot. Choose another depot for them first.” | DEPOT_IN_USE | You are turning a depot that deliveries ship from into a plain place. | Change their Ships from first. |
| “The main depot is a depot. Make another depot the main depot first.” | MAIN_DEPOT_KIND | You are turning the main depot into a plain place. | Choose Make main on another depot, then try again. |
| “Only a depot can be the main depot.” | MAIN_DEPOT_KIND | You tried to make a place the main depot. | Choose a depot. |
| “The main depot cannot be deleted. Make another depot the main depot first.” | MAIN_DEPOT | The main depot cannot be deleted. | Make another depot the main depot, then delete this one. |
| “An example depot cannot be the main depot.” | EXAMPLE_NOT_MAIN | You tried to make the example depot the main depot. | Choose one of your depots. |
| “Example deliveries already exist for this day.” | EXAMPLES_EXIST | The example deliveries for this date were already added. | Choose another day, or use the existing examples. |
| “Your own records already use an identifier the examples need.” | IDENTIFIER_CONFLICT | One of your vehicles, deliveries or depots has an identifier the examples use. | Rename it if you want to add the examples. |
| “A calculation is waiting or running. Wait for it to finish or cancel it, then try again.” | JOB_ACTIVE | Example data is not removed while a calculation is waiting or running. | Wait for it or cancel it in Planning, then choose Remove example data again. |
| “Your own vehicles or deliveries name an example depot. Choose another for them first.” | EXAMPLE_PLACE_IN_USE | Your own vehicles or deliveries name the example depot in Starts at, Ends at or Ships from. | Give them another depot or place, then remove the examples. |
4. CSV import
| Message | Code | Cause | What to do |
|---|---|---|---|
| “CSV limit is 1 MiB.” | UPLOAD_TOO_LARGE | The file is larger than 1 MiB. | Split the file. |
| “Request body limit is 1 MiB.” | REQUEST_TOO_LARGE | The HTTPS proxy refused a request larger than 1 MiB. | Send a smaller file or fewer records. |
| “Send UTF-8 CSV as text/csv.” | CSV_REQUIRED | A script sent the file with another content type. | Send the file as text/csv. |
| “CSV must be UTF-8.” | — | The file uses another encoding. | Save it again as UTF-8. |
| “This file separates its columns with semicolons; Tournevia reads commas. Save it with commas as separators, then preview it again.” | — | The file’s columns are separated by semicolons, as spreadsheets set to French conventions save CSV. | Save the file again with commas as separators, then preview it again. |
| “Expected exact headers: …, optionally followed by: …” | — | The header row differs from the expected columns. | Copy the header row with Copy the header row under Columns of the file, or start from Download the template; see CSV formats. |
| “Maximum 250 data rows.” | — | The file has more than 250 data rows. | Split the file. |
| “Column count differs from headers.” | — | A row has more or fewer cells than the header. | Check separators and quotes in that row. |
| “Malformed CSV quoting or oversized field.” | — | A quote is not closed, or a cell is too long. | Correct the quoting in that row. |
| “Provide at least one data row.” | — | The file has only a header. | Add the records. |
| “Duplicate identifier within upload.” | — | The same identifier appears twice in the file. | Keep one row per identifier. |
| “Use a nonnegative whole number in the stated unit.” | — | A number cell has a sign, a decimal, a space or a unit. | Write digits only, in the column’s unit. |
| “Use true or false.” | — | active has another value. | Write true or false. |
| “Provide both numeric latitude and longitude, or leave both empty.” | — | Only one coordinate, or a non-numeric one, is given. | Fill in both, or leave both empty. |
| “Write working hours as 07:30-17:00, or leave the cell empty for a day off.” | — | A weekday column (monday … sunday) does not have the expected format. | Write HH:MM-HH:MM, or leave the cell empty. |
| “No saved customer has this code.” | — | The customer column names an unknown customer. | Correct the code, or save the customer first. |
| “No depot or place has this code.” | — | start, end or ships_from names an unknown code. | Correct the code, or add the depot or place in Settings › Depots and places. |
| “Only example vehicles and deliveries use an example depot.” | — | The row names the example depot. | Choose one of your depots or places. |
| “A delivery ships from a depot, not from another place.” | — | ships_from names a place. | Name a depot, or leave the cell empty. |
| “Existing identifier has different values; use a version-checked edit.” | — | A script imported, without update_existing=true, a row that changes an existing record. The interface’s import shows such a row as Changed instead. | Send update_existing=true, or change that record in its editor. |
| “Address lookup was unavailable, so rows without coordinates have no location.” | — | The address service did not answer during the preview. | Import the rows and place their pins, or preview again later. |
| “Address lookup ran out of time, so some rows without coordinates have no location.” | — | The lookups for this file took longer than the import allows (20 s). | Place the remaining pins, or split the file and preview again. |
Rows to check
These warnings in the delivery import preview do not block the import. Their code is in the API response.
| Message | Code | What to do |
|---|---|---|
| “The service date … is in the past.” | PAST_DATE | Check the row’s date. |
| “No coordinates, and the address was not looked up. Place the pin after the import.” | NO_LOCATION | Address search is off or stopped: place the pin after the import. |
| “The address was not found. Place the pin after the import.” | ADDRESS_NOT_FOUND | Check the address, or place the pin after the import. |
| “Only the town or place was found (…), so no point was placed.” | ADDRESS_VAGUE | Complete the address with the number and street, or place the pin after the import. |
| “Only an uncertain match was found (…, … %), so no point was placed.” | ADDRESS_UNCERTAIN | Correct the address, or place the pin after the import. |
| “Latitude and longitude look swapped: in France latitude is about 41 to 51 and longitude about -5 to 10.” | COORDINATES_SWAPPED | Swap the two columns in the file. |
| “… km from the depot. Check the address or the coordinates.” | FAR_FROM_DEPOT | The point is more than 100 km from the depot the delivery ships from, or from the nearest of your depots: check it. |
| “The same address has another point in row ….” | SAME_ADDRESS_ELSEWHERE | Two rows with the same address have points more than 300 m apart: keep the right one. |
| “This point is … m from the entrance saved for customer ….” | CUSTOMER_POINT_DIFFERS | The file’s point is more than 50 m from the customer’s entrance: remove the coordinates to use the customer’s, or review the point. |
5. Calculation
| Message | Code | Cause | What to do |
|---|---|---|---|
| “Every selected delivery and the depot require reviewed coordinates.” | LOCATION_NOT_REVIEWED | A selected delivery or the main depot has no reviewed point. | Choose Review locations, review each entrance, then calculate again. |
| “Example vehicles and deliveries are planned only with other examples. Select only examples, or only your own records.” | EXAMPLES_MIXED | The selection mixes records marked Example with your own. | Deselect one of the two kinds. |
| “No depot or place has this code.” | PLACE_UNKNOWN | A selected vehicle or delivery names a depot or place that no longer exists. Concerned: names the codes. | Correct Starts at, Ends at or Ships from, then calculate again. |
| “Review the entrance of every depot and place the selected vehicles start or end at before calculating.” | PLACE_NOT_REVIEWED | The entrance of one of these depots or places is not reviewed. Concerned: names the codes. | Review them in Settings › Depots and places, then calculate again. |
| “Some selected vehicles do not work on the planning day. Check their weekly hours and days off in Fleet.” | VEHICLE_OFF_DAY | The named vehicles have a day off that day, or no hours on that weekday. | Change their hours in Fleet, or deselect them. |
| “Select active records with windows and delivery dates inside the planning day.” | INVALID_SELECTION | A selected record is inactive (a cancelled delivery, for example), or its window or date is outside the planned day. | Check the date and the selected records. |
| “Calculations support at most three exact truck profiles.” | MODEL_LIMIT | The selected vehicles have more than three different combinations of dimensions, weights and axles. | Select vehicles that share at most three routing profiles. |
| “Calculations support at most 301 distinct points: 250 for deliveries and the rest for depots and places.” | MODEL_LIMIT | Too many distinct entrances are selected. | Select fewer deliveries, or fewer vehicles starting from different places. |
| “The depot and the selected deliveries are farther apart than this installation's routing allows in one calculation. Select deliveries closer together, or ask your installation operator about the distance limit.” | AREA_TOO_WIDE | Two of the calculation’s places (the main depot, depots and places where routes start or end, deliveries) are farther apart than the installation’s routing allows (200 km by default). Concerned: names the two farthest. | Leave out the far deliveries or plan them separately, or ask the operator about the limit. |
| “This company already has the maximum of five calculations waiting or running. Wait for one to finish or cancel one, then submit again.” | QUEUE_FULL | A company can have five calculations waiting or running at once. | Wait, or choose Cancel calculation on one of them. |
| “Selected source versions changed. Reload records and select again.” | SOURCE_CHANGED | A selected record or the main depot changed after you selected it. | Reload, check the selection and calculate again. |
| “This calculation has already finished.” | JOB_FINISHED | The cancellation arrived after the end. | Open its result. |
| “Enter whole minutes from 0 to 120.” | — | In Settings › Calculation, the safety margin is not a whole number of minutes from 0 to 120. | Correct the value, then choose Save the safety margin. |
When a calculation ends without a result, the screen shows Calculation could not finish (or Calculation cancelled), the message below, and advice under What to do next. Your saved deliveries, vehicles and earlier plans are unchanged.
| Message | Code | What to do next |
|---|---|---|
| “Calculation cancelled. No result was saved.” | CANCELLED | “Nothing was saved. Start a new calculation when you are ready.” |
| “Whole-job time budget exceeded; no result published.” | JOB_TIMEOUT | “The calculation exceeded its time limit. Select fewer deliveries or vehicles, or ask your installation operator to raise JOB_TIMEOUT_SECONDS.” |
| “Worker stopped. Start a new calculation explicitly.” or, for a recalculation, “Previous worker stopped before saving a result. The edit was not applied; retry explicitly.” | WORKER_INTERRUPTED | “The calculation worker stopped during this calculation. Start a new calculation; if it happens again, contact your installation operator.” |
| A message naming the vehicles, deliveries, depots or places concerned, for example an off-road pin, or “Routing or solver failed. Check saved coordinates, engine coverage and service availability; then start a new calculation.” | ENGINE_FAILED | “Correct the records named above (pins, vehicles or assignments) and start a new calculation. If no record is named, check that the routing service is running.” When deliveries are named, Review deliveries opens them. |
| “A database operation failed during this calculation; no result was published. Retry explicitly.” | DATABASE_ERROR | “The result could not be saved. Contact your installation operator before retrying.” |
| “Late result rejected: job is no longer running.” | JOB_NOT_RUNNING | “This calculation was stopped before it finished. Nothing was saved; start a new calculation.” |
| “Calculation process stopped unexpectedly. Check local engine availability and retry explicitly.” | CALCULATION_FAILED | “Review the current inputs and retry the calculation. If the service remains unavailable, contact your installation operator.” |
| “Calculation output missing or too large; no draft accepted.” or “Calculation logs exceeded their bounded output budget.” | OUTPUT_LIMIT | Same advice as above. |
| “Saved job input is invalid. Reload source records and submit again.” | INPUT_INVALID | Same advice as above. |
6. Review, Ready, route sheets and export
| Message | Code | Cause | What to do |
|---|---|---|---|
| “Review unassigned work and explicitly accept this partial plan.” | UNASSIGNED_NOT_ACCEPTED | Some deliveries are unassigned and the partial plan was not accepted. | Review them, then tick I accept the unassigned deliveries in this partial plan. |
| “Another Ready plan for this day already dispatches some of the same vehicles or deliveries.” | READY_CONFLICT | Two Ready plans would dispatch the same work. | Choose Keep the other plan, or Replace the other Ready plan, which returns it to Draft. |
| “Deliveries, vehicles or the depot changed after this calculation. Start a new calculation before marking it Ready or exporting.” | SOURCE_CHANGED | A delivery or vehicle in the plan was changed, cancelled or deleted, or the main depot or a depot or place in use changed. The server answers “Selected source records changed. Start a fresh calculation from current sources.” or “Depot changed. Start a fresh calculation from current sources.” | Start a new calculation from the current records. |
| “Correct this draft and obtain a complete passing recalculation first.” | VALIDATION_FAILED | The result is stale, failed validation or has blocking issues. | Correct the blocking issues and recalculate. |
| “Independent re-validation failed: …” | VALIDATION_FAILED | Checking the saved plan again found the issues named. | Correct them and recalculate. |
| “No deliveries were served; there is nothing to dispatch.” | NO_SERVED_WORK | No route has a stop. | Check vehicles, windows and capacities, then recalculate. |
| “Mark this current plan ready before export.” | PLAN_NOT_READY | Only a Ready plan has route sheets and an export. | Choose Mark ready, then print or export. |
| “Recalculation is pending. Existing route display is stale.” | PLAN_BUSY | A recalculation of this plan is still running. | Wait for its result. |
| “This plan already has an active edit. Wait for its result.” | PLAN_BUSY | Another edit of this plan is being recalculated. | Wait for its result. |
| “Plan changed. Reload before finalizing.”, “Plan changed. Reload before downloading.” or “Plan changed. Reload its current version before editing.” | PLAN_CHANGED | The plan was changed elsewhere since you opened it; the second message also applies to route sheets. | Reload the plan and review it again. |
| “The saved plan changed after you began editing. Reload the draft before submitting another edit.” | — | Someone saved this plan while you were moving stops. | Choose Keep my moves on the latest version, or Discard changes. |
| “Assign every plan delivery exactly once to a selected vehicle or the unassigned list.” | INVALID_ASSIGNMENT | An edit does not place each delivery once. | Reload the plan and move the stops again. |
| “Existing routes, times and geometry are stale. Finalization and export are disabled.” | — | A recalculation is pending, or the last one failed and the edit was not applied. | Wait, or recalculate. |
| “… would exceed its … capacity.”, “… would exceed its limit of … stops.”, “… lacks equipment required by ….” or “… ships from …; … starts at ….” | — | Move-panel warnings: the destination vehicle does not suit the moved delivery. | Choose another vehicle, or recalculate for the full validation. |
| “This vehicle has no route in this plan.” | NOT_FOUND | The route sheet asked for is for a vehicle without deliveries in this plan. | Open the sheets of every vehicle with Print the route sheets. |
| “Route sheets are unavailable.” | — | The sheets could not be loaded. | Choose Back to the plan, reload the plan and try again. |
| “Synthetic plans cannot be finalized or exported as operational routes.” | SYNTHETIC_NOT_OPERATIONAL | The plan comes from the old local demonstration mode without accounts. Plans of examples in a company workspace are not affected. | Plan in a company workspace. |
A blocking issue shows a title, for example “Vehicle does not start at the depot the delivery ships from”, and its technical detail with the vehicles and deliveries involved. Inspect vehicle and stops opens the route concerned.
Reasons shown for unassigned deliveries
| Reason | Code | What to do |
|---|---|---|
| “No compatible vehicle” | NO_COMPATIBLE_VEHICLE | No selected vehicle has all of the required equipment, enough capacity in all five quantities and, when the delivery ships from a depot, a start at that depot. Select or adjust a vehicle. |
| “No road usable by the compatible trucks within 50 m of the pin. Move the pin to the vehicle entrance and review it.” | NO_ROAD_NEAR_PIN | Move the pin to an entrance on a road these trucks can use, then review it. |
| “No route in the routing dataset” | NO_ROUTE_IN_DATASET | The road data has no route between where the compatible trucks start or end and this entrance. Check the pin. |
| “Not assigned within the calculation budget” | SOLVER_UNASSIGNED | It did not fit the windows, capacities, working hours or route limits. If “Route limits were reached: …” is shown, raise or remove them in Fleet. If “Calculated with a … min safety margin before each window ends. …” is shown, the margin may be why: an administrator can lower it in Settings › Calculation before a new calculation. |
| “Manually unassigned” | MANUALLY_UNASSIGNED | You moved it to Unassigned. Move it to a vehicle if it should be served. |
7. Connection and service
| Message | Code | Cause | What to do |
|---|---|---|---|
| “The server could not be reached. Your changes have not been confirmed; check the connection and try again.” | — | The browser could not reach the server. | Check the network, then retry. Your entries are still on screen. |
| “The service returned an unreadable response. Your changes have not been confirmed. Retry the same submission if it was pending.” | — | The answer could not be read as the application’s, for example a page returned by a proxy. | Retry the same submission. |
| “The planning service is not responding. Try again in a moment.” | SERVICE_UNAVAILABLE | The HTTPS proxy could not reach the application. | Retry in a moment; if it lasts, contact the operator. |
| “Database unavailable; check migrations and database service.” | — | The application cannot use its database. | Contact the operator. |
| Calculation service needs attention: “The calculation worker is not running. New calculations will wait in the queue until the worker is started.” | — | The worker is stopped. | Contact the operator. Queued calculations start once it runs. |
| Calculation service needs attention: “The routing service is unavailable. Calculations and road-access checks will fail until the routing service is running.” | — | The routing service does not answer. | Contact the operator. |
| “Send the current quoted version in If-Match.” | VERSION_REQUIRED | A script sent a change without the record’s version. The interface always sends it. | See the API reference. |
| “If-Match must be one quoted positive integer.” | INVALID_VERSION | The version header is malformed. | Send the version in quotes, for example "3". |
| “Supply Idempotency-Key; reuse it only for an identical submission retry.” or, for an edit, “Supply Idempotency-Key for safe edit submission retries.” | IDEMPOTENCY_REQUIRED | A script submitted a calculation or an edit without a retry key. | See the API reference. |
| “Use a 1–128 character printable ASCII idempotency key without spaces.” | INVALID_IDEMPOTENCY_KEY | The retry key is empty, too long or has spaces. | Use a key that follows the rule. |
| “This key was already used for a different request.” | IDEMPOTENCY_CONFLICT | The same retry key was sent with different content. | Use a new key for a new request. |
| “Give service_date to find vehicles that do not work that day.” | SERVICE_DATE_REQUIRED | A script filtered the fleet for vehicles that do not work, without a date. | Add service_date to the request. |
The code RESULT_CONTEXT reports an internal mismatch between a plan and its records; it should not appear. If a message is not listed here, read troubleshooting or ask your installation operator, giving the code and the time.