Error Codes ​

Any error that contains {0} or {1} represents some of the data that the user entered into the request, an example is error 1001 user id {0} does not exist, the {0} would be 1d7fa573-ee72-4fdc-8dd9-68011b8693e3.

Default Errors ​

1000 - Unknown Error ​

Error code 1000 is an unknown error, unfortunately there is no way to tell what has caused this issue.

    {
        code: 1000,
        message: "UnknownError"
    }

    {
        code: 1000,
        message: "UnknownError"
    }

User Errors ​

1001 - User Id Does Not Exist ​

This error is caused by supplying a User Id to a request when the User Id does not exist, to fix this error make sure the id is correct and make sure the user does exist.

    {
        code: 1001,
        message: "User Id {0} does not exist"
    }

    {
        code: 1001,
        message: "User Id {0} does not exist"
    }

1002 - User Reference Does Not Exist ​

This error is caused by supplying a User Reference to a request when the user id cannot be matched to a user in the system, to fix this error make sure the reference is correct and make sure the user does exist.

    {
        code: 1002,
        message: "User reference {0} does not exist"
    }

    {
        code: 1002,
        message: "User reference {0} does not exist"
    }

1003 - User Reference Is Already In Use ​

This error is caused by supplying a User Reference to a POST or PUT user request where the User to a user in the system, to fix this error make sure the reference is correct and make sure the user does exist.

    {
        code: 1003,
        message: "User reference {0} is already in use"
    }

    {
        code: 1003,
        message: "User reference {0} is already in use"
    }

1004 - User Name Is Already In Use ​

This error is cause by supplying a Username in a request when the Username already exists, to fix this choose a different user name.

    {
        code: 1004,
        message: "Username {0} is already in use"
    }

    {
        code: 1004,
        message: "Username {0} is already in use"
    }

1007 - User Status Already Set ​

This error is cause by the User Status already being set to the status you are trying to set it to, to avoid this error don't set a user to the same status.

    {
        code: 1007,
        message: "User id {0} is already set to {1}"
    }

    {
        code: 1007,
        message: "User id {0} is already set to {1}"
    }

1008 - Line Manager Does Not Exist ​

This error is caused by supplying a Line Manager id to a request where the id does not exist, to fix this error check if the id is correct and make sure the line manager exists.

    {
        code: 1008,
        message: "Manager id {0} does not exist"
    }

    {
        code: 1008,
        message: "Manager id {0} does not exist"
    }

1009 - Assessor Does Not Exist ​

This error is caused by supplying an Assessor id to a request where the id cannot be matched to any other assessor in the system, to fix this error check if the id is correct and make sure the assessor exists.

    {
        code: 1009,
        message: "Assessor id {0} does not exist"
    }

    {
        code: 1009,
        message: "Assessor id {0} does not exist"
    }

1010 - System Role Does Not Exist ​

This error is caused by supplying a System Role to a request where the system role does not exist, to fix this error check the system role id for any incorrect digits and check that the system role exists.

    {
        code: 1010,
        message: "System role {0} does not exist"
    }

    {
        code: 1010,
        message: "System role {0} does not exist"
    }

1011 - Error Retrieving Error Safety Critical Status ​

This error is caused by supplying a User id to the update user safety critical status endpoint where the User id cannot be matched with a user in the system, to fix this error make sure the User id has the correct digits and that the User id being referenced exists on a User.

    {
        code: 1011,
        message: "Error retrieving safety critical status for user {0}"
    }

    {
        code: 1011,
        message: "Error retrieving safety critical status for user {0}"
    }

1012 - Error Retrieving Authority To Work Status ​

This error is caused by supplying an authority to work status id to a request where it cannot be found, to fix this error make sure the authority to work id does not have any incorrect digits and check if the error retrieving authority to work status exists.

    {
        code: 1012,
        message: "Error retrieving authority to work status for user {0}"
    }

    {
        code: 1012,
        message: "Error retrieving authority to work status for user {0}"
    }

1013 - Standard Support Level Missing ​

This error is caused by supplying a support level reference to a request where the reference does not match any standard support levels in the system, to fix this error check for any spelling mistakes within the reference and check if the support level exists.

    {
        code: 1013,
        message: "The Support Level {0} is not available."
    }

    {
        code: 1013,
        message: "The Support Level {0} is not available."
    }

1014 - Not Applicable Authority To Work Status Missing ​

This error is caused by supplying an authority to work status reference to a request where the reference cannot be matched with any authority to work status in the system, to fix this error check for any spelling mistakes within the reference and check if the authority to work status exists.

    {
        code: 1014,
        message: "The Authority to Work Status {0} is not available."
    }

    {
        code: 1014,
        message: "The Authority to Work Status {0} is not available."
    }

1015 - Not Applicable Safety Critical Status Missing ​

This error is caused by supplying a safety critical status id to POST User request where the id does not match a safety crictcal status id in the system, to fix this check the id for any incorrect digits and if it does exist in the system.

    {
        code: 1015,
        message: "The Safety Critical Status {0} is not available."
    }

    {
        code: 1015,
        message: "The Safety Critical Status {0} is not available."
    }

1016 - Default Competency Cycle For Role Missing ​

This error is caused when supplying a company role id to the POST User endpoint where the company role id supplied does not exist on any of the competency cycles in the system, to fix this check the id for any incorrect digits and if the company role id does exist on a competency cycle within the system.

    {
        code: 1016,
        message: "There is no default Competency Cycle for {0}"
    }

    {
        code: 1016,
        message: "There is no default Competency Cycle for {0}"
    }

1017 - User Is Under Age ​

This error is caused when validating the age of a user that is under the age of {1}, to fix this if this is a mistake change the user's birthday to the correct date, if not the user is not able to use the system.

    {
        code: 1017,
        message: "User {0} is underage. They must be {1} or over."
    }

    {
        code: 1017,
        message: "User {0} is underage. They must be {1} or over."
    }

1018 - System User Not Set ​

This error occurs within a few endpoints Skill POST and PUT as well as POST asssessment note and PUT Archive user medical details, it happens due the a property on the object being created or updated within the request being set to the system user id this property is some form of Archived or modified by user id, to fix this make sure the system user has being set up.

    {
        code: 1018,
        message: "A system user has not been set up."
    }

    {
        code: 1018,
        message: "A system user has not been set up."
    }

1019 - Support Level Missing ​

This error occurs when a request is made to POST User and a support level id that cannot be matched to any in the system is supplied to the request body, to fix this ensure all of the digits inside of the id are correct and that the support level exists in the system.

    {
        code: 1019,
        message: "Support Level Status {0} does not exist"
    }

    {
        code: 1019,
        message: "Support Level Status {0} does not exist"
    }

1020 - Authority To Work Status ​

This error occurs when a request is made to check if the authority to work status exists, where the id supplied to the request cannot be matched to an authority to work status in the system.

    {
        code: 1019,
        message: "Authority to Work Status {0} does not exist"
    }

    {
        code: 1019,
        message: "Authority to Work Status {0} does not exist"
    }

1021 - Safety Critical Status Missing ​

This error occurs when a request is made to check if the safety critical status exists where the id supplied cannot be matched to a safety critical status in the system.

    {
        code: 1019,
        message: "Authority to Work Status {0} does not exist"
    }

    {
        code: 1019,
        message: "Authority to Work Status {0} does not exist"
    }

Address Errors ​

2001 - Address Id Does Not Exist ​

This error is caused when supplying an address id to a request where the id does not match an address in the system, to fix this check the id for any spelling mistakes.

    {
        code: 2001,
        message: "Address Id {0} does not exist"
    }

    {
        code: 2001,
        message: "Address Id {0} does not exist"
    }

2002 - Cannot Find Address For User ​

This error is caused when the address supplied to a request cannot be found on a user, to fix this make sure the address exists on the user.

    {
        code: 2002,
        message: "Cannot find a valid address for this user {0}"
    }

    {
        code: 2002,
        message: "Cannot find a valid address for this user {0}"
    }

Department Access Errors ​

3005 - User Already Has Department Access ​

This error is caused when attempting to allowing a user that already has access to department {1} access to department {1}, to avoid this error do not assign a user access to a department they already have access to.

    {
        code: 3005,
        message: "User id {0} already has access to {1}"
    }

    {
        code: 3005,
        message: "User id {0} already has access to {1}"
    }

3006 - User Does Not Have Department Access ​

This error is caused when attempting to remove a user’s access to a department they already do not have access to, to avoid this error check if a user is assigned to a department before attempting to remove them.

    {
        code: 3006,
        message: "User id {0} does not have access to {1}"
    }

    {
        code: 3006,
        message: "User id {0} does not have access to {1}"
    }

Location Errors ​

4001 - Location Id Does Not Exist ​

This error occurs when a location id is supplied to a request where the id cannot be matched with an existing location in the system, to fix this check the id for wrong digits and check if the location does exist.

    {
        code: 4001,
        message: "Location id {0} does not exist"
    }

    {
        code: 4001,
        message: "Location id {0} does not exist"
    }

4002 - Location Reference Does Not Exist ​

This error occurs when a location reference is supplied to a request where the reference cannot be matched with an exist location in the system, to fix this check the reference for spelling mistakes.

    {
        code: 4002,
        message: "Location reference {0} does not exist"
    }

    {
        code: 4002,
        message: "Location reference {0} does not exist"
    }

4003 - Location Id Is Already In Use ​

This error occurs when a user supplies a location id to an add location request when the id supplied already exists on a location in the system, to fix this use a different id.

    {
        code: 4003,
        message: "Location id {0} is already in use"
    }

    {
        code: 4003,
        message: "Location id {0} is already in use"
    }

4004 - Location Id Is Assigned To A Department ​

This error occurs when attempting to delete a location that is already assigned to a department, to fix this remove the location from the associated department.

    {
        code: 4004
        message: "Location id {0} is assigned to a department"
    }

    {
        code: 4004
        message: "Location id {0} is assigned to a department"
    }

4005 - Location Id Is Assigned To User Base Location ​

This error occurs when a user attempts to delete a location that is already assigned to a user's base location, to fix this remove the location from the associated user's base location.

    {
        code: 4005
        message: "Location id {0} is assigned to a user base location"
    }

    {
        code: 4005
        message: "Location id {0} is assigned to a user base location"
    }

4006 - Location Id Is Assigned To A User's Permanent Address ​

This error occurs when a user attempts to delete a location that is already assigned to user's permanent address, to fix this remove the location from the associated user's permanent address.

    {
        code: 4006
        message: "Location id {0} is assigned to a user permanent address"
    }

    {
        code: 4006
        message: "Location id {0} is assigned to a user permanent address"
    }

Competency Errors ​

5000 - Competency Unit Does Not Exist ​

This error occurs when a request is made where a competency unit id is supplied that does not match any competency units in the system, to fix this check the id for a mismatch digit.

    {
        code: 5000
        message: "Competency Unit {0} does not exist"
    }

    {
        code: 5000
        message: "Competency Unit {0} does not exist"
    }

5001 - Competency Element Does Not Exist ​

This error occurs when a request is made where a Competency element id is supplied that does not match any competency element in the system, to fix this check the id for a mismatch digit.

    {
        code: 5001
        message: "Competency Element {0} does not exist"
    }

    {
        code: 5001
        message: "Competency Element {0} does not exist"
    }

5002 - No Competency Unit Name Provided ​

This error occurs when a request is made to insert a new competency unit where a name has not been provided, to fix make sure a name is present before sending the request.

    {
        code: 5002
        message: "No Competency Unit name provided."
    }

    {
        code: 5002
        message: "No Competency Unit name provided."
    }

5004 - Competency Element Order Should Start At Zero ​

This error occurs when a request is made to check the element order and the first element's index is not zero, to fix this make sure that the beginning element has an index of zero.

    {
        code: 5004
        message: "Starting Element Order Index should be 0."
    }

    {
        code: 5004
        message: "Starting Element Order Index should be 0."
    }

5005 - Competency Elements Should Have Sequential Order ​

This error occurs when a request is made to check the element order and the elements are not in sequential order, to fix this make sure that all the elements' indexes are in sequential order.

    {
        code: 5005
        message: "Competency Elements Should be ordered sequentially and incrementally."
    }

    {
        code: 5005
        message: "Competency Elements Should be ordered sequentially and incrementally."
    }

5007 - Competency Element Name Is Null ​

This error occurs when a request is made to insert elements and an element to be inserted does not have a name, to fix this error make sure to provide all elements with name.

    {
        code: 5007
        message: "Competency Element must have a name."
    }

    {
        code: 5007
        message: "Competency Element must have a name."
    }

5008 - Competency Criteria Order Should Start At Zero ​

This error occurs when the first criteria in a list of criteria does not have an index of 0, to fix this make sure the first criteria has an index of 0.

    {
        code: 5008
        message: "Starting Competency Criteria Index should be 0"
    }

    {
        code: 5008
        message: "Starting Competency Criteria Index should be 0"
    }

5009 - Competency Criteria Should Have Sequential Order ​

This error occurs when a request is made to check the criteria order and the criteria are not in sequential order, to fix this make sure that all the criteria indexes are in sequential order.

    {
        code: 5009
        message: "Competency Criteria should have a sequential incremental order"
    }

    {
        code: 5009
        message: "Competency Criteria should have a sequential incremental order"
    }

5010 - Competency Criteria Starting Incorrect Index ​

This error occurs when a list of competency criteria starts at a number which is not 0, to fix this make sure the list beginning index is 0.

    {
        code: 5009
        message: "Competency Criteria should have a sequential incremental order"
    }

    {
        code: 5009
        message: "Competency Criteria should have a sequential incremental order"
    }

5011 - Competency Criteria Name Is Null ​

This error occurs when a competency criteria to be inserted into an element does not have a name, to fix this make sure to provide a name to the competency criteria before inserting them into an element.

    {
        code: 5011
        message: "No Competency Criteria name provided."
    }

    {
        code: 5011
        message: "No Competency Criteria name provided."
    }

5012 - Competency Elements Already Exist ​

This error occurs when attempting to insert a competency element(s) to a competency unit where the element(s) already exists, to fix this make sure when inserting an element/elements, it/they has not already been inserted.

    {
        code: 5012
        message: "Competency Unit Already has Competency Elements"
    }

    {
        code: 5012
        message: "Competency Unit Already has Competency Elements"
    }

5013 - Competency Cycle Does Not Exist ​

This error occurs when a user is assigning to competency cycle that does not exist, to fix this make sure the id of cycle has the correct digits and check if the cycle exists within the system.

    {
        code: 5013
        message: "Competency Cycle {0} does not exist."
    }

    {
        code: 5013
        message: "Competency Cycle {0} does not exist."
    }

5014 - Competency Element Already In Position ​

This error occurs when a competency element has been assigned an index that is already taken by another element that is already present within the competency unit, to fix the make sure that the element index provided is not present on another element that is already within the competency unit.

    {
        code: 5014
        message: "The Competency Unit already has an element at this position."
    }

    {
        code: 5014
        message: "The Competency Unit already has an element at this position."
    }

Department Errors ​

6001 - Department Id Does Not Exist ​

This error occurs when a department id is supplied to a request where the id does not match with any in the system, to fix this check for any incorrect digits within the id and check if the department is in the system.

    {
        code: 6001
        message: "Department Id {0} does not exist"
    }

    {
        code: 6001
        message: "Department Id {0} does not exist"
    }

6002 - Department Code Does Not Exist ​

This error occurs when attempting to get a department by code where the code does not match with any in the system, to fix this check for any spelling mistakes.

    {
        code: 6002
        message: "Department Id {0} does not exist"
    }

    {
        code: 6002
        message: "Department Id {0} does not exist"
    }

6003 - Department Code Already Exists ​

This error occurs when attempting to add or update a department with a code that is already on an existing department, to fix this choose a different code.

    {
        code: 6003
        message: "Department with code {0} already exists"
    }

    {
        code: 6003
        message: "Department with code {0} already exists"
    }

6004 - Department Location Does Not Exist ​

This error occurs when adding or updating a department with a location that does not exist, to fix this check for any incorrect digits on the location id and check if the location exists.

    {
        code: 6004
        message: "Location Id {0} does not exist"
    }

    {
        code: 6004
        message: "Location Id {0} does not exist"
    }

Role Errors ​

7001 - Role Id Does Not Exist ​

This error occurs when a role id is supplied to a request where the id cannot be matched with any roles in the system, to fix these issues check for any incorrect digits of the id role and check if the role exists.

    {
        code: 7001
        message: "Role id {0} does not exist"
    }

    {
        code: 7001
        message: "Role id {0} does not exist"
    }

7002 - Role Reference Does Not Exist ​

This error occurs when a role reference is supplied to a request but cannot be matched with a role in the system, to fix these issues check the reference for any spelling mistakes and check if the role exists.

    {
        code: 7002
        message: "Role reference {0} does not exist"
    }

    {
        code: 7002
        message: "Role reference {0} does not exist"
    }

7003 - Role Id Already In Use ​

This error occurs when attempting to create a new role where the id used already exists on a role, to fix this error change the id.

    {
        code: 7003
        message: "Role id {0} is already in use"
    }

    {
        code: 7003
        message: "Role id {0} is already in use"
    }

7004 - Role Id In Use With ​

This error occurs when attempting to delete a role that is referenced somewhere else e.g., an assessment or competency cycle, to fix this remove the role from the places that it is used.

    {
        code: 7004
        message: "Role Id {0} is in use with {1}"
    }

    {
        code: 7004
        message: "Role Id {0} is in use with {1}"
    }

Team Errors ​

8001 - Team Id Does Not Exist ​

This error occurs when a team id is supplied to a request, but the id cannot be matched with any team in the system, to fix this check the id for incorrect digits and check if the team exists.

    {
        code: 8001
        message: "Team id {0} does not exist"
    }

    {
        code: 8001
        message: "Team id {0} does not exist"
    }

8002 - Team Reference Does Not Exist ​

This error occurs when a team reference is supplied to a request, but the reference cannot be matched with any team in the system, to fix this check the reference for mispellings and check if the team exists.

    {
        code: 8002
        message: "Team reference {0} does not exist"
    }

    {
        code: 8002
        message: "Team reference {0} does not exist"
    }

8003 - Team Id Is Already In Use ​

This error occurs when attempting to add a team that has the id of a team that already exists, to fix this error use a different id that is not already associated with a team.

    {
        code: 8003
        message: "Team id {0} is already in use"
    }

    {
        code: 8003
        message: "Team id {0} is already in use"
    }

Orr Doctor Information Errors ​

9001 - Orr Doctor Information Id Does Not Exist ​

This error occurs when attempting to get an orr doctor by id, but the id does not match any of the orr doctor id's in the system, to fix this check the id for incorrect digits and check if the orr doctor exists.

    {
        code: 9001
        message: "OrrDoctorInformation id {0} does not exists"
    }

    {
        code: 9001
        message: "OrrDoctorInformation id {0} does not exists"
    }

9002 - Orr Doctor Information Id Is Already In Use ​

This error occurs when adding an orr doctor with an id that already exists on an orr doctor in the system, to fix this provide a different id.

    {
        code: 9002
        message: "OrrDoctorInformation id {0} is already in use "
    }

    {
        code: 9002
        message: "OrrDoctorInformation id {0} is already in use "
    }

User Medical Detail Errors ​

10001 - User Medical Detail Does Not Exist ​

This error occurs when a user medical detail id is supplied to a request that cannot be matched with a user medical detail in the system, to fix this check the id for incorrect digits and check the user medical detail exists.

    {
        code: 10001
        message: "UserMedicalDetail id {0} does not exist"
    }

    {
        code: 10001
        message: "UserMedicalDetail id {0} does not exist"
    }

10002 - User Medical Detail Id Is Already In Use ​

This error occurs when attempting to create a user medical detail with an id that already matches an entry in the system, to fix this error choose a different error.

    {
        code: 10002
        message: "UserMedicalDetail id {0} is already in use"
    }

    {
        code: 10002
        message: "UserMedicalDetail id {0} is already in use"
    }

Skill Errors ​

11001 - Skill Id Does Not Exist ​

This error occurs when a skill id is supplied to a request, but it cannot be matched with any skills in the system, to fix this check the id for incorrect digits and check if the skill.

    {
        code: 11001
        message: "Skill Id {0} does not exist"
    }

    {
        code: 11001
        message: "Skill Id {0} does not exist"
    }

11002 - Skill Duration Unit Id Does Not Exist ​

This error occurs when a duration unit id is supplied to a skill create or update request, but it cannot be matched to any other duration unit ids in the system, to fix this check the id for incorrect digits and check if the duration unit exists.

    {
        code: 11001
        message: "Duration Unit Id {0} does not exist"
    }

    {
        code: 11001
        message: "Duration Unit Id {0} does not exist"
    }

11003 - Skill Company Role Does Not Exist ​

This error occurs when a company role id is supplied to a skill create or update request, but the id of the company role cannot be matched with any in the system, to fix this check the id for incorrect digits and check if the company role exists.

    {
        code: 11003
        message: "Company Role Id {0} does not exist"
    }

    {
        code: 11003
        message: "Company Role Id {0} does not exist"
    }

Assessment Errors ​

12001 - Assessment Id Does Not Exist ​

This occurs when an assessment id is supplied to a request, but it cannot be matched with any assessments in the system, to fix this check the id for incorrect digits.

    {
        code: 12001
        message: "Assessment Id {0} does not exist"
    }

    {
        code: 12001
        message: "Assessment Id {0} does not exist"
    }

12002 - Assessment Assessing User Id Does Not Exist ​

This error occurs when a user id supplied in a request to create a new assessment cannot be matched with a user in the system, to fix this check the id for incorrect digits and if the user being assessed exists.

    {
        code: 12002
        message: "User Id {0} for user being assessed does not exist"
    }

    {
        code: 12002
        message: "User Id {0} for user being assessed does not exist"
    }

12003 - Assessment Assessor User Id Does Not Exist ​

This error occurs when an assessor user id is supplied in a request to create a new assessment, but the id of the assessor user cannot be matched with an entry in the system, to fix this check the id for incorrect digits and if the assessor user exists.

    {
        code: 12003
        message: "Assessor user Id {0} does not exist"
    }

    {
        code: 12003
        message: "Assessor user Id {0} does not exist"
    }

12004 - Company Role Id Does Not Exist ​

This error occurs when a company role id is supplied to a request, but the company role cannot be matched with a company role in the system, to fix this check the id for incorrect digits and if the assessor user exists.

    {
        code: 12004
        message: "Company role Id {0} does not exist"
    }

    {
        code: 12004
        message: "Company role Id {0} does not exist"
    }

12005 - Competency Cycle Id Does Not Exist ​

This error occurs when providing a competency cycle id to a request that cannot be matched with a competency cycle in the system, to fix this check the id for incorrect digits and if the competency cycle exists.

    {
        code: 12005
        message: "Competency cycle Id {0} does not exist"
    }

    {
        code: 12005
        message: "Competency cycle Id {0} does not exist"
    }

12006 - Assessment Type Id Does Not Exist ​

This error occurs when creating a new assessment and providing an assessment type id that cannot be matched with an assessment type in the system, to fix this check the id for incorrect digits and if the assessment type exists.

    {
        code: 12006
        message: "Assessment Type Id {0} does not exist"
    }

    {
        code: 12006
        message: "Assessment Type Id {0} does not exist"
    }

12007 - Assessment Competency Id Does Not Exist ​

This error occurs when completing an assessment with a competency id that cannot be matched with a competency in the system, to fix this check the id for incorrect digits and if the assessor user exists.

    {
        code: 12007
        message: "Assessment competency Id {0} does not exist"
    }

    {
        code: 12007
        message: "Assessment competency Id {0} does not exist"
    }

Assessments Note Errors ​

13001 - Assessment Note Id Does Not Exist ​

This error occurs when a request has been provided an assessment note id that cannot be matched with an assessment note in the system, to fix this check the id for incorrect digits and check if the assessment note exists.

    {
        code: 13001
        message: "Assessment note Id {0} does not exist"
    }

    {
        code: 13001
        message: "Assessment note Id {0} does not exist"
    }

13002 - Assessment Note Assessment Id Does Not Exist ​

This error occurs when a request has been provided the id for an assessment and the id does not match any assessments in the system, to fix this check the id for incorrect digits and check if the assessment exists.

    {
        code: 13002
        message: "Assessment Id {0} does not exist"
    }

    {
        code: 13002
        message: "Assessment Id {0} does not exist"
    }

Reference Errors ​

14001 - System Role Id Does Not Exist ​

This error occurs when sending a request to get a system role by id, but the id cannot be matched to a system role in the system, to fix this check the id for incorrect digits and if the system role exists.

    {
        code: 14001
        message: "System Role {0} does not exist"
    }

    {
        code: 14001
        message: "System Role {0} does not exist"
    }

14002 - Support Level Id Does Not Exist ​

This error occurs when sending a request to get a support level by id, but the id cannot be matched to a support level in the system, to fix this check the id for incorrect digits and if the support exists.

    {
        code: 14002
        message: "Support Level {0} does not exist"
    }

    {
        code: 14002
        message: "Support Level {0} does not exist"
    }

14003 - Employee Authority To Work Status Id Does Not Exist ​

This error occurs when supplying a get authority to work status by id request with an id that does not match with any of the authority to work statuses in the system, to fix this check the id for incorrect digits and if the authority to work status exists.

    {
        code: 14003
        message: "Employee Authority To Work Status {0} does not exist"
    }

    {
        code: 14003
        message: "Employee Authority To Work Status {0} does not exist"
    }

14004 - Employee Safety Status Id Does Not Exist ​

This error occurs when supplying a get safety status by id request with an id that does not match with any of the safety statuses in the system, to fix this check the id for incorrect digits and if the safety status exists.

    {
        code: 14004
        message: "Employee Safety Status {0} does not exist"
    }

    {
        code: 14004
        message: "Employee Safety Status {0} does not exist"
    }

14005 - Duration Unit Does Not Exist ​

This error occurs when supplying a request with a duration unit id that cannot be matched in the system to a duration unit, to fix this check the id for incorrect digits and if the duration unit exists.

    {
        code: 14005
        message: "Duration Unit Id {0} does not exist"
    }

    {
        code: 14005
        message: "Duration Unit Id {0} does not exist"
    }

14006 - Assessment Competency Does Not Exist ​

This error occurs when supplying a get assessment competency by id with an id that cannot be matched with any in the system, to fix this check the id for incorrect digits and if the assessment competency exists.

    {
        code: 14006
        message: "Assessment Competency {0} does not exist"
    }

    {
        code: 14006
        message: "Assessment Competency {0} does not exist"
    }

14007 - Assessment Type Does Not Exist ​

This error occurs when supplying a get assessment type by id request with an id that cannot be matched with any assessment types in the system, to fix this check the id for incorrect digits and if the assessment type exists.

    {
        code: 14007
        message: "Assessment Type {0} does not exist"
    }

    {
        code: 14007
        message: "Assessment Type {0} does not exist"
    }

14008 - Assessment Type Category Does Not Exist ​

This error occurs when a request to get an assessment type category by id, is supplied with an id that cannot be matched to any assessment type category in the system, to fix this check the id for incorrect digits and if the assessment type category exists.

    {
        code: 14008
        message: "Assessment Type Category {0} does not exist"
    }

    {
        code: 14008
        message: "Assessment Type Category {0} does not exist"
    }

14009 - Platform Does Not Exist ​

This error occurs when a request to get a platform by id, is supplied with an id that cannot be matched to any platforms in the system, to fix this check the id for incorrect digits and if the platform exists.

    {
        code: 14009
        message: "Platform {0} does not exist"
    }

    {
        code: 14009
        message: "Platform {0} does not exist"
    }

Company Information Errors ​

15001 - Company Information Does Not Exist ​

This error code occurs when sending a request to get company information, but the company information does not exist, to fix this check if the company information exists.

    {
        code: 15001
        message: "The company information cannot be retrieved."
    }

    {
        code: 15001
        message: "The company information cannot be retrieved."
    }

Support Plan Type Error ​

16001 - Support Plan Type Does Not Exist ​

This error occurs when sending a request to get a support plan by id where the id cannot be matched with any support plans in the system, to fix this check the id for incorrect digits and if the support plan exists.

    {
        code: 16001
        message: "Support Plan Type with Id {0} does not exist"
    }

    {
        code: 16001
        message: "Support Plan Type with Id {0} does not exist"
    }

Support Plan Approval Type Errors ​

17001 - Support Plan Approval Type Does Not Exist ​

This error occurs when sending a request to get a support plan approval type by id where the id cannot be matched with any support plan approval types in the system, to fix this check the id for incorrect digits and if the aupport plan approval type exists.

    {
        code: 17001
        message: "Support Plan Approval Type with Id {0} does not exist"
    }

    {
        code: 17001
        message: "Support Plan Approval Type with Id {0} does not exist"
    }

Traction Errors ​

18001 - Traction Does Not Exist ​

This error occurs when sending a request to get a traction by id or code where the id or code cannot match with any tractions in the system, to fix this check the id for incorrect digits and if the traction exists.

    {
        code: 18001
        message: "Traction {0} does not exist"
    }

    {
        code: 18001
        message: "Traction {0} does not exist"
    }

18002 - Traction With Code Already Exists ​

This error occurs when a traction code is supplied to a POST or PUT traction endpoint where the code already exists on a traction within the system, to fix this error use a different code as the system does not allow tractions to have a code where the code exists on a traction already in the system.

    {
        code: 18002
        message: "A Traction with code {0} already exists."
    }

    {
        code: 18002
        message: "A Traction with code {0} already exists."
    }

18003 - Traction With Name Already Exists ​

This error occurs when checking the traction name availability where the name is already taken by another traction already in the system, to fix this error supply a name to the request that is not already present on a traction within the system.

    {
        code: 18003
        message: "A Traction with name {0} already exists."
    }

    {
        code: 18003
        message: "A Traction with name {0} already exists."
    }

18004 - Traction Duration And Unit Required ​

This error occurs when sending a request to the POST or PUT traction endpoint, if the traction is set to expire the traction is checked if it is valid this process checks to see if the duration and the duration unit id are present.

If so it checks to see if any of the duration units within the system have the same id provided to the request body if the first or second check is not passed then this error code is returned, to fix this error supply a valid duration and duration unit id to the traction.

    {
        code: 18004
        message: "Traction is set to expire, a duration and duration unit are required."
    }

    {
        code: 18004
        message: "Traction is set to expire, a duration and duration unit are required."
    }

18005 - Traction Duration And Unit Not Required ​

This error occurs when sending a request to the POST or PUT traction endpoint where the traction does not exipre but contains values for duration and duration unit id.

If the traction is set to expire the traction is checked to see if it contains a duration and duration unit, if the traction is set to NOT expire then it should not contain any values for duration or duration unit id.

To fix this error when creating to traction remove any value from the duration fields if the traction is NOT set to expire.

    {
        code: 18005
        message: "Traction does not expire, duration and duration unit should be null."
    }

    {
        code: 18005
        message: "Traction does not expire, duration and duration unit should be null."
    }

18006 - Traction Duration Unit Does Not Exist ​

This error occurs when a duration unit id supplied to a request cannot be matched with any in the system, to fix this error make sure that the duration unit id supplied does not have any incorrect digits and the duration unit the id refers to exists.

    {
        code: 18006
        message: "Duration unit id {0} does not exist"
    }

    {
        code: 18006
        message: "Duration unit id {0} does not exist"
    }

18007 - Traction Is Already In Use ​

This error occurs when a traction id is supplied to a request to create a traction where the id already exists on a traction, to fix this use a different id.

    {
        code: 18007
        message: "Traction id {0} is already in use"
    }

    {
        code: 18007
        message: "Traction id {0} is already in use"
    }

Infrastructure Authorized ​

19001 - Infrastructure Authorised To Operate Id Does Not Exist ​

This error occurs when supplying a get infrastructure authorised to operate id request with an id that cannot be matched in the system, to fix this check the id for incorrect digits and check if the infrastructure authorised to operate exists.

    {
        code: 19001
        message: "Infrastructure Authorised To Operate Id {0} does not exist"
    }

    {
        code: 19001
        message: "Infrastructure Authorised To Operate Id {0} does not exist"
    }

User Company Role Errors ​

20001 - User Already Has Company Role ​

This error occurs when adding a user company role to a user that already has that company role, to fix this do not assign a user a company role they already have.

    {
        code: 20001
        message: "User with Id: {0} already has Role with Id: {1}"
    }

    {
        code: 20001
        message: "User with Id: {0} already has Role with Id: {1}"
    }

20002 - User Company Role Does Not Exist ​

This error occurs when supplying a company role id to a request where the id cannot be matched to a user company role in the system, to fix this check the id supplied for any incorrect digits and check if the user company role the id refers to exists.

    {
        code: 20002
        message: "User Company Role with Id {0} doesn't exist"
    }

    {
        code: 20002
        message: "User Company Role with Id {0} doesn't exist"
    }

Routes Errors ​

21000 - Route Does Not Exist ​

This error occurs when supplying a request a route id or code that cannot be matched with any routes in the system, to fix this check the id for any incorrect digits and check if the route exists.

    {
        code: 21000
        message: "Route: {0} does not exist"
    }

    {
        code: 21000
        message: "Route: {0} does not exist"
    }

21003 - Route Duration And Unit Required ​

This error occurs when checking for valid duration details the details are set to expire, to fix this error set the duration and duration unit to valid values that aren't incorrect and exist in the system.

    {
        code: 21003
        message: "Route is set to expire, a duration and duration unit are required"
    }

    {
        code: 21003
        message: "Route is set to expire, a duration and duration unit are required"
    }

21004 - Route Duration And Unit Not Required ​

This error occurs when checking for valid duration details on a route with no expiry so the duration should be null, to avoid this error make sure routes that do not expire do not contains any duration or duration units.

    {
        code: 21004
        message: "Route does not expire, duration and duration unit should be null"
    }

    {
        code: 21004
        message: "Route does not expire, duration and duration unit should be null"
    }

21005 - Route With Code Already Exists ​

This error occurs when creating a route with a code that already exists on a route, to fix this error choose another code that is not already taken by another route.

    {
        code: 21005
        message: "A Route with code {0} already exists"
    }

    {
        code: 21005
        message: "A Route with code {0} already exists"
    }

21006 - Route With Title Already Exists ​

This error occurs when creating a route with a title that already exists on a route, to fix this error choose another title that does not already exist on a route.

    {
        code: 21006
        message: "A Route with title {0} already exists."
    }

    {
        code: 21006
        message: "A Route with title {0} already exists."
    }

Safety Brief Errors ​

30001 - Safety Brief Does Not Exist ​

This error occurs when supplying a request with a safety brief id that cannot be matched with any safety brief in the system, to fix this check the id for incorrect digits and if the safety brief exists.

    {
        code: 30001
        message: "Safety Brief Id {0} does not exist"
    }

    {
        code: 30001
        message: "Safety Brief Id {0} does not exist"
    }

30002 - Safety Brief With Title Already Exists ​

This error occurs when creating or updating a safety brief with a title that already exists on another safety brief, to fix this error use a title that does not already exist on another safety brief.

    {
        code: 30002
        message: "Safety Brief with Title {0} already exists"
    }

    {
        code: 30002
        message: "Safety Brief with Title {0} already exists"
    }

Safety Brief Type Errors ​

40001 - Safety Brief Type Id Does Not Exist ​

This error occurs when supplying a get safety brief type by id request with an id that cannot be matched with a safety brief type in the system, to fix this check the id for incorrect digits and if the safety brief type exists.

    {
        code: 40001
        message: "Duration Unit Id {0} does not exist"
    }

    {
        code: 40001
        message: "Duration Unit Id {0} does not exist"
    }