| Confirm interface with Street Manager | |
The following tables document common errors observed when exchanging information with Street Manager, what may have caused the error and possible ways to fix the issue.
Errors that occurred during notice export can be seen on the Transfer Issues section of the Street Works > Transfer tab.
* Note that in a number of cases additional notices may need to be manually added into Street Manager to bring Street Manager and Confirm in-sync with one-another. These changes will be imported into Confirm which may result in some Ignored notices.
| Error Message | Cause | How to Fix |
|---|---|---|
| A HA can only imposed changes on a granted permit | Have attempted to issue an Authority Imposed Variation on a permit that has not yet been granted in Street Manager | Check the transfer status of the previous Grant sent from Confirm to ensure that was sent to Street Manager. Make any manual corrections necessary in Street Manager*. |
| A highway authority officer can only grant/refuse permits that have not already been granted, refused, revoked or cancelled. Permit has no pending changes | Permit may have already deemed in Street Manager due to changes in deeming rules | No action required. Unsent Grant/Refuse in Confirm will be overwritten with the next notice received from Street Manager |
| A highway authority officer can only request a permit modification on permits with a status of submitted. | Modification Requests are only valid where there is no current permit. Note: Only one Modification Request can be raised on a Permit Application.
|
Refuse the most recent change from Street Manager with reasons. The promoter will still have their previously granted / deemed permit. |
| A PAA can not be altered | Street Manager currently treats the first application for all Major works as a PAA, even if the works are not asset activity, which can cause notices to become out of sync with Confirm. | Grant the PAA in Street Manager and re-send the Modified Application from Confirm which will be treated like a Permit Application in Street Manager. |
| A permit modification can only be requested on permits with a work category of standard, minor, major or hs2_highway | Modification requests cannot be sent in response to Immediate Permits | Either refuse the permit or issue an Authority Imposed Variation |
| A planner can only alter permits with a status of granted. <br>An active alteration already exists for this permit record | Once a Variation has been sent for an existing permit then this must be granted, refused or deemed before a subsequent variation can be sent | Wait for the previous variation to be granted |
| A planner can only cancel permits with a status of submitted | Street Manager is out of sync with Confirm | Compare the Street Manager history with the Confirm history to determine where the notices went out of sync and make corrections in Street Manager* |
| A Promoter or HA imposed change can not be assessed | It is possible that the permit has already been granted in Street Manager | Compare the Street Manager history with the Confirm history to determine where the notices went out of sync and make corrections in Street Manager* |
| Access restricted | The promoter does not have access to the necessary workstream for the works | Check that the Confirm Promoter API user has access to the workstream for the works (3rd to 5th digit of the works reference) |
| Additional change ... added since grant | Confirm has detected that a further change has been logged in Street Manager since the version that was reviewed and Granted in Confirm | Review the most recent changes to the Permit and re-assess |
| Bad Request. additional_comments is required | Notice comments must be supplied when refusing or revoking permits | Add comments and re-send |
| Bad Request. Date must be in the future | Forward planning notices cannot be submitted retrospectively | Re-plan the works and send a Forward Planning or PAA as appropriate |
| Bad Request. pending_change_details is required | A Modification Request has been sent without any proposed changes | Add necessary changes to the Notification comments and re-send |
| Bad Request. The maximum duration for proposed works allowed is 5 years. Please make sure your timings fall within the permitted range. | Self explanatory | Double-check the dates on the works |
| Cannot add a reinstatement as the work status is not in progress, completed or non-notifiable | Works start may not have transferred to Street Manager | Check Street Manager history and add a works start if necessary* |
| Coordinates are mandatory | Self explanatory | May need to run an Error Correction wizard to add coordinates to a legacy works |
| Forbidden | Some characters in a descriptive field are deemed as suspicious by Street Manager. This is determined by a Street Manager security algorithm, so it is not possible to give a simple list of words / characters to avoid. | Check log files and contact technical support |
| Forward plans can only be sent for major works to Street Manager. | Street Manager does not allow Forward Plans for other works categories | Send a normal permit application when due |
| No changes have been made to the permit | A variation of some kind has been sent with no relevant changes. Note this can also occur with Authority Imposed Variations where no valid NCT codes are included in the Notice Comments. | Use Compare with latest in the Confirm history to investigate. For Authority Imposed Variations Street Manager only allows Conditions to be imposed and these must be prefixed by valid NCT codes in the text entered into Confirm. Ensure that NCT codes do not contain spaces and that leading zeros are included where appropriate, e.g. "NCT04b" |
| No Street Manager Authority credentials found for Organisation .... | Attempting to perform an authority action for an organisation where no Authority credentials are configured | Check that the DfT Ref 1 of the Street Authority Organisation for the Permit is set correctly |
| No Street Manager Promoter credentials found for Organisation ... | Attempting to perform an promoter action for an organisation where no Promoter credentials are configured. Confirm currently does not support Contractor credentials. Note: For contractors, please use Promoter credentials instead.
|
Check that the DfT Ref 1 of the Woks Promoter Organisation for the Permit is set correctly |
| Not found | Not able to find the referenced works in Street Manager | Check log files for the earliest mentions of this works reference and contact technical support |
| permit_status must be submitted, granted or permit_modification_request in order to update the actual_start_date | Street Manager may have treated the first application from Confirm as a PAA | Create and Grant a Permit application in Street Manager and re-submit the actual start notice |
| Street Manager notification not implemented for: E42700 | Street Manager does not currently support Temporary Traffic Signal applications | Agree a suitable alternative application process with the Highway Authority |
| Work has no active permit | Permit / variation may have already deemed in Street Manager | Check permit status in Street Manager |
| You can't add a reinstatement unless an excavation has been carried out | Requires excavation flag in Street Manager is not checked | Revert the works stop (if required) and create a change in Street Manager to enable the excavation. When this is granted re-submit the works stop and the registration. |
| Exported to Street Manager: Waiting for the Actual Inspection to be created | Defective Apparatus details (Section 81s) are only sent to Street Manager when the inspection is exported. | See the inspections section to check if the Inspection has exported |
| Cannot vary a closed Permit. | Street Manager does not allow a permit to be varied after the Works Stop | Revert the Works Stop, submit the Variation, wait for it to be Granted and re-submit the Works Stop |
| Only PAA can be raised after a forward planning information. | Street Manager does not allow Forward Planning notices to be used on anything other than major works | Re-run the Planned Works wizard and force the notice type to Major so that a PAA is generated. |
| "Unknown object type: sw_header..." message when trying to create the next notice | If the first two notices for a works have been created in quick succession but the first notice fails due to some error then both notices have their send flag un-ticked. Confirm is then not able to determine what the logical next notice should be. | To avoid this issue, ensure that the previous notice has been been sent before sending follow-up notices. If this issue occurs the Confirm team can provide SQL to flag the first notice as "notionally" sent which then allows a Modified Application to be sent to correct the original error. |
| Duration Challenge is not valid in this scenario | If a Duration Challenge is sent independently from the Grant or is not valid in the scenario then the Confirm Duration Challenge notice will not send and will have this transfer warning | Please see the field mapping section on Granting with a Duration Challenge and refer to the Street Manager business rules on when this is allowed. |
| Bad Request. reasonable_period_end_date must be on or after the original reasonable_period_end_date and before the proposed_end_date | If a Grant with Duration Challenge is created in Confirm for any Variation notice but the reasonable period is not as per the rules set by Street Manager then only Grant is sent individually and Duration Challenge is marked unsent with transfer warning as - 'Duration Challenge is not valid in this scenario'. | Please see the field mapping section on Granting with a Duration Challenge and refer to the Street Manager business rules on when this is allowed. |
| Bad Request. emergency_contact_name should not be empty. emergency_contact_number should not be empty | If Emergency Name and Emergency Phone are blank for 'Traffic Control (Multi-Way Signals)' or 'Traffic Control (Two-Way Signals)' in Web Settings then permit is not exported with a transfer warning. | Update Emergency Name and Emergency Phone for 'Traffic Control (Multi-Way Signals)' or 'Traffic Control (Two-Way Signals)' in Confirm Web Settings. |
Errors that occurred during notice import will be received via email. Once the cause of the error is resolved you can prompt Confirm to re-import the data by making any change to the works, e.g. adding a works comment.
| Error Message | Cause | How to Fix |
|---|---|---|
| A site status with an external ref of E4Depth4 / 8 could not be found | If a depth of zero is received from Street Manager then the DfT Ref on your Confirm Site Status codes is used to flag the site as abandoned or subsumed. This error indicates that these DfT Refs. have not been set | The "Subsumed" site status (typically with a code of "SUBS") should have a DfT Ref. of "E4Depth4" and your "Abandoned" Site Status (typically with a code of "S08") should have a DfT ref. of "8". |
| Object reference not set to an instance of an object. (Number of possible causes) | Legacy works has a Works Comment that was never exported (has no Batch Number) | Contact Confirm team for SQL to delete the unsent comments |
| Original works was imported as a Confirmation notice due to a previous bug | Ask the promoter to cancel the current works and re-submit the permit application | |
| Works not found in Confirm | Unable to import a follow-up notice due to a previous failure | Determine the cause of the failure to import the original notice |
| Not found party/organisations/.../workstreams/... | The works reference does not match the normal pattern. On importing a works into Confirm for an organisation we do not recognise we assume that the 3rd to 5th digit of the works reference correspond to the workstream in street manager. If the works reference is badly formed then this cannot be found and we can't import the permit | Ask the promoter to re-submit the works using a valid works reference |
| Site wasn't found in Confirm. Usrn ... not found and no provisional street configured | USRN was not found in Confirm. | Check the status of the Gazetteer in Confirm and ensure that a Provisional Street is set up on the Street Works System Settings screen |
| Street Works Notice ... truncated to ... characters. Original value: ... | Some fields in Confirm cannot hold the full length of text that could be sent from Street Manager | Be aware of the truncation when reviewing the works |
| Unsent notice in Confirm is overwritten by any incoming notice. | Since the notice is unsent (draft mode) so any notice on top of it overwrites it. | In Transfer tab's Transfer Warnings field, we store some of the information of overwritten notice for future use. |
Errors that occurred during comment export can be seen by clicking on the Send To button and selecting the Street Manager recipient.
| Error Message | Cause | How to Fix |
|---|---|---|
| Not found | Attempting to send a works comment against a works that does not exist in Street Manager | If the comment relates to a Defective Apparatus notice then re-send the original apparatus inspection. If the comment relates to a works that you did not promote then either ask the promoter to transition the works to Street Manager or log an historic inspection on the works to re-create the historic works in Street Manager. The comment will re-send on the run after the works was created in Street Manager. |
Inspection errors can be viewed by clicking the Batch button on the inspection toolbar. To re-send an inspection untick and re-tick the Send Inspection checkbox, Save the inspection and respond "Yes" to the prompt to send an update for the Primary Inspection.
| Error Message | Cause | How to Fix |
|---|---|---|
| Bad Request. failure_reason_details is required |
1. Failed inspection item does not have any notes and there are no Defect notes 2. Confirm will automatically remove any items that are not applicable to the inspection category before sending to Street Manager. For example, Backfill inspection items are not allowed on a Defect Follow-up inspection |
1. Add notes to the item or Defect Notes and re-send the inspection 2. Go through the process of logging the inspection in Street Manager to determine the allowed inspection items for the category (no need to save the inspection) and ensure that only these items are used. It is advisable to update your Inspection Categories in Confirm to remove Inspection Groups that are not valid for Street Manager |
| Inspection category: ... does not map to a valid Street Manager inspection category. | Inspection category cannot be sent to Street Manager | Check DfT references on Inspection Categories in Confirm against the field mapping tables in this document. Note: Street Manager does not support Investigatory (core sample) inspections. Use Third-party or Routine instead |
| Inspection Outcome: Passed/Abortive does not map to a valid Street Manager Section81 Severity. No Street Manager Promoter credentials found for Organisation ... | Sending a second inspection on a Defective Apparatus that was previously sent over EToN | The only workaround at present is to re-raise the Defective Apparatus under a different reference (and untick the send flag of any pending inspections / notices under the old reference) |
| 'officer_contact_details' is required | No phone number has been specified for the Inspecting officer | Add a suitable phone number or email address to "Telephone Number" field of the Inspecting Action Officer |
| "To be processed". No error or batch number | Inspections are only sent from organisations you initiate for to organisations that have the EToN Export flag checked. Note that for Defective Apparatus and Unattributable works the "to" organisation is the inspecting authority | Check the EToN Export flag for the recipient. Note before changing this contact the Confirm team to obtain SQL to check for legacy inspections that might also get exported if this flag is changed |
| Request failed with status code 404 | Can occur if an historic inspection is against a USRN that is no longer valid in Street Manager | Correct the USRN on the parent works using a suitable notice, e.g. Error Correction or Defective Apparatus, and then re-send the inspection. |
| 'works_coordinates' is required | Can occur if an historic inspection is against a works that did not have original coordinates | Ensure that an Easting and Northing are specified on the Inspection and re-send it. |
| Investigatory does not map to a valid Street Manager inspection category. | Can occur if 'Investigatory' Category is selected instead of new Investigatory Categories to export to Street Manager. | Use the new Investigatory Categories intended for exporting Inspection to Street Manager. |
Errors that occurred during inspection import will be received via email. Once the cause of the error is resolved you can prompt Confirm to re-import the data by making any change to the works, e.g. adding a works comment.
| Error Message | Cause | How to Fix |
|---|---|---|
| cannot insert NULL into actual_inspection.officer_code The INSERT statement conflicted with the FOREIGN KEY constraint "act_inspection_fk1_officer" | All received inspections are logged against the Inspection Officer set on the Inspection Import System Settings screen | Ensure that the setting is populated with a valid Action Officer |
| Cannot perform atomic update as objects previous state was not supplied | This can happen if the next inspection number for a works (managed internally) gets out of sync | Obtain SQL to fix this from the Confirm team |
FPN errors can seen in the Notes on the Offence tab or can be viewed by clicking the Issue / Withdraw Batch button.
Note that FPNs that have failed to send will still show with a status of "Penalty Sent Queue". Once corrections have been made you will need to click Resend from the Actions menu.
| Error Message | Cause | How to Fix |
|---|---|---|
| Offence Type: An offence under s.... does not map to a valid Street Manager Offence Code. | Street Manager does not support Notice offences | Re-send the FPN via email or post |
| 'officer_contact_details' is required | No phone number has been specified for the Penalty Action Officer Officer | Add a suitable phone number or email address to "Telephone Number" field of the Action Officer specified on the Penalty tab |
| Cannot read property 'length' of undefined | This can occur if no withdrawal reason is supplied | Add a reason to the Offence Notes and resend the Withdrawal. |
| 'works_coordinates' is required | Can occur if an historic FPN is against a EToN works that did not have original coordinates | Log a Received ("paper") error correction notice on the works to set its coordinates and then re-export the FPN |
Errors that occurred while performing some Actions from Street Works ConfirmWeb screen.
| Error Message | Cause | How to Fix |
|---|---|---|
| Maximum 10 Ancillary coordinate can be added on the Map section. | If user plot more than 10 coordinates on the Map, they will get an Error pop-up on the Modal Window. | User has to replot the Ancillary coordinates on the Map Section. |
| Maximum 20 Ancillary records can be added on the Permit Application. | If user add more than 20 Ancillary records on the Permit Application, they will get an Error pop-up. | Only 20 Ancillary records are allowed to be added on the Permit Application |
| Failed to process the request. | When Street Manager service is unavailable. | Try reloading the page once the service is available. |
| Joint site meeting date must occur today or in the future. | Joint Site meeting can't be done in past. | Update date time in today or future. |
| 'Must be between 1 and 1000' while updating Chargeable Days in Lane Rental Assessment modal window | Chargeable days can't be more than 1000 for Chargeable Days in Lane Rental Assessment modal window. | Update Chargeable days between 1 and 1000. |
| Reasonable period end date must be between the original reasonable period end date and proposed end dates while updating New Reasonable Period End Date in Duration Challenge Response Modal window. | Reasonable period end date not updated between the original reasonable period end date and proposed end dates. | Update Reasonable period end date between the original reasonable period end date and proposed end dates. |