Skip to content
Last updated

Error codes and severity levels

CodeMessageSeverityDetails
10000Orchestration created successfullyIReturned by API response on create orchestration.
10001No orchestration data foundCReturned by API response on create orchestration if orchestration data is not passed. Orchestration request is rejected.
10002Invalid trade typeCReturned by API response on create orchestration if trade type code is not recognized. Orchestration request is rejected.
10003Invalid port codeCReturned by API response on create orchestration if port code is not recognized. Orchestration request is rejected.
10004Container# {container number} is invalidCReturned by API response on create orchestration if container number does not match the expected format. Orchestration request is rejected.
10005Missing Bill of LadingCReturned by API response on create orchestration if Bill of Lading is not passed. Orchestration request is rejected. If Bill of Lading is passed, but does not match SprintPass Pro’s records, the Guarantee Through Date will be removed from the orchestration to block accidental payments.
10006Invalid Guarantee Through DateCReturned by API response on create orchestration if Guarantee Through Date does not match the expected format. Orchestration request is rejected.
10007Missing Guarantee Through DateWReturned by API response and notifications. Payment orchestration will not be initiated. Even if passed correctly, this error will appear in notifications if Bill of Lading does not match.
10008Invalid preferencesCReturned by API response. Orchestration request is rejected.
10009Orchestration not foundCReturned by API on update orchestration if the orchestration does not exist. Request is rejected.
10010Orchestration canceled successfullyIReturned by API response on orchestration cancelation request. All orchestration activities will be stopped.
10011Appointment canceled successfullyIReturned by API response on appointment cancelation request. Orchestration will continue to report status and process payments if applicable.
10012{Internal Appointment System message} [{Internal Appointment System code}]IReturned by notifications on events received by the internal appointment system.
10013{Internal Appointment System message} [{Internal Appointment System code}]WReturned by notifications on events received by the internal appointment system, i.e. no time slots found but orchestration keeps looking, or truck identification required prior to pick up.
10014{Internal Appointment System message} [{Internal Appointment System code}]CReturned by notifications on events received by the internal appointment system, i.e. no time slots found and threshold exceeded all the options. This error requires action as the appointment attempt has failed and will not be retried.
10015Non-matching Bill of LadingWReturned by notifications. This message is installed if passed BoL does not match SprintPass Pro’s records. Also, if SprintPass Pro has no record of the BoL.
10016Missing container numberCReturned by API response on orchestration creation request. Request is rejected.
10017Missing trade typeCReturned by API response on orchestration creation request. Request is rejected.
10018Missing locations listCReturned by API response on orchestration creation request. Request is rejected.
10019Missing port codeCReturned by API response on orchestration creation request. Request is rejected.
10020An orchestration is already active for this containerCReturned by API response on orchestration creation request if the container is already orchestrated by another party. Request is rejected.
10021Container not found.CReturned by API response on container status request.
10022Terminal not supported for paymentsWReturned by notifications after the container is located at terminal where payments are not supported. Orchestration keeps running normally for all supported features.
10023Terminal not supported for paymentsCReturned by API response on orchestration update request if Guarantee Through Date is provided. Request is rejected.
10024Terminal not supported for appointmentsWReturned by notifications after the container is located at terminal where appointments are not supported. Orchestration keeps running normally for all supported features.
10025Terminal not supported for appointmentsCReturned by API response on orchestration update request if any appointment preferences are provided. Request is rejected.
10026Unexpected error: reference code#[reference code]CReturned by API response and notifications whenever an unexpected error occurs. Manual support required.
10027An orchestration for this container is active for another companyCReturned by API response on orchestration creation request if the container is already orchestrated. Request is rejected.
10028Terminal payments not supported. Only third party will be processedWReturned by notifications after the container is located at terminal where payments are not supported, except for third party such as PierPass & CleanTruck. Orchestration keeps running normally for all supported features.
10029Orchestration update request acceptedIReturned by API response on successful orchestration update request.
10030Empty return not allowed by the terminalWReturned by notifications if the terminal does not support empty returns and empty return preferences were passed. Other orchestration features continue to execute normally.
10031Updates cannot be passed during a reschedule requestWReturned by API response on orchestration update request if more fields were passed other than time preferences. Only time preferences will be taken. Other fields will be ignored. Reschedule will be processed normally.
10032Appointment not found in given locationCReturned by API response on orchestration update or cancelation request if no appointment is found for that container.
10033Appointment cannot be updated while awaiting response from internal appointment systemCReturned by API response on orchestration update request if appointment data is passed and the system is waiting to receive acknowledgement of a previous appointment operation. Integrator should retry in this case.
10034Container has moved to off-dock yardIReturned by notifications if the container has moved to an off-dock location.
10035An empty container cannot be the primary in a dual moveCDual moves need to be implemented by adding an Empty on top of an existing pick appointment.
10036This container has a dual move appointment.CThe container requested as a dual is already in a dual orchestration.
10037Not implemented yetCNot implemented yet.
10038Invalid secondary containerCDual container does not exist or is not gated out yet. For Duals, only gated out empty containers are supported.
10039No terminals identified to receive empty line typeCEven though there are terminals supporting Empty reception, non of them accept this particular container.
10040Terminal not identified to receive empty line typeW