Overview
When a Digital Waste Tracking message fails it displays the basic "Failed Reason" at the top.
You can also click on the Failed Reason tab for more precise details (it is these that will be referenced in the below entries)
Note: This article is currently in progress and will be updated by the Support team as new solutions are identified and confirmed.
Common Errors
The below are examples of common Failed reasons, what they mean and how to resolve them.
Reading item numbers in errors: the numbers in errors such as "wasteItems[26]" are counted from 0, because that is how DEFRA's API numbers list items. So wasteItems[0] is the first waste item, wasteItems[1] is the second, and wasteItems[26] is the 27th item on the submission. Weighsoft shows the error as DEFRA returns it, so this cannot be changed in Weighsoft.
Missing access token (company/outlet/default credentials not configured)
This error indicates that Weighsoft was unable to authenticate with DEFRA's API to submit the waste tracking data. The reason is usually an incorrect or missing entry in the Digital Waste Settings
The simplest solution for this is to clear all the settings and hit save, then re-enter them using the below details which have been obtained directly from Defra and have been proven to work successfully:
Authentication API Url: https://waste-movement-external-api-75ee2.auth.eu-west-2.amazoncognito.com/oauth2/token
Organisation ID: Use the API ID sent to you by Defra
Client ID: 5i4gmksh5eds98bpcs7467vv4l
Secret ID: 1kvj709eommh12p8n3ci6idfab5tnigbf9j5dp11oomf04c9siub
These need to be entered in both Settings>General>Digital Waste Tracking and in Lookups>Companies
Once these details have been correctly entered the API will be able to establish a link and send messages.
"apiCode" must be a valid GUID
This error message will be returned if the organisation ID entered into the settings is not in the correct format.
Theses IDs are typically in the format of "8 digits - 4 digits - 4 digits - 4 digits - 12 digits" (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).
If your ID is not in this format you will need to contact Defra to confirm the correct code.
Failed Reason: "wasteItems[0].physicalForm" must be one of [Gas, Liquid, Solid, Powder, Sludge, Mixed]
This error suggests that the Waste Product set against the Transaction has no "State" set against it. To fix the issue go to Lookups>Products, locate the product and select the "State" field (selecting from Solid, Liquid, gas etc) in the bottom-right. Then click Save.
If the Main product already has a State in place then it is also worth checking the products listed in the Components tab of the Transaction.
Once all the products and component products have a "State" set against them you can resend the DWT message.
There is a known issue that is fixed in Weighsoft versions 5.544.6 and above. IN earlier versions the system looked at a field on the Transaction rather than the waste product itself. After 5.544.6 the system will refer to the State set against the product in all instances except tickets for the Hazardous module (where it will instead first refer to the Physical State set against the item).
Waste tracking id=xxxxx has no waste items
This message appears if the ticket in question has no products on that are marked as a Waste Type in Lookups>Products
Possible scenarios:
The product listed on the ticket has not been marked as a "Waste Type" in Lookups>Products
The product on the ticket is legitimately not a waste type, but the Transaction itself has bene set to an Activity Code of "Waste In" (this will cause it to be picked up by DWT regardless).
"carrier.address.xxxxxxx" is not allowed to be empty
This can read "carrier.address.fullAddress", "carrier.emailAddress" or "carrier.phoneNumber".
This means that the field in question against the supplier used on the transaction is empty in Lookups>Supplier.
This is a known issue that is fixed in Weighsoft versions 5.544.6 and above. After that version these field are "optional" and so can be left blank.
"carrier.emailAddress" or "carrier.phoneNumber" is not allowed to be empty — workaround for pre-5.544 systems
If you are running Weighsoft version 5.544.6 or above, carrier email and phone are treated as optional and this error should not occur. See the callout below.
If you are running a version below 5.544.6, these fields are required by DEFRA even though they appear optional in the Weighsoft interface. To resolve before upgrading:
Go to Lookups>Suppliers>Haulier and locate the supplier used on the failing transaction
Enter an email address and phone number in the relevant fields
Save and then resend the failed DWT record from Administration>Digital Waste Tracking
This is a known issue that is fixed in Weighsoft versions 5.544.6 and above. After that version, carrier email and phone are optional and can be left blank without causing submission failures.
"carrier.address.postcode" must be in valid UK or Ireland format
This error indicates an issue with the post code set against the Supplier linked to the job.
Quite often it is a case of having spaces before or after the postcode.
To resolve this you need to go to the supplier in Lookups>Suppliers and ensure the postcode is correct and doe snot have any leading or trailing spaces.
"wasteItems[xxx].weight.amount" must be a positive number
This will come up if the Netweight of a waste item is equal to of less than 0.
Possible Scenarios
The item in question has been mistakenly set with a NetWeight of 0 or less and needs to be amended.
The item is flagged as "Bulky" in Lookups>Products and thus has a unit of Each and no Netweight.
This is a known issue that is fixed in Weighsoft versions 5.544.12 and above. At that point Bulky item with the "EACH" unit of sale are ignored by the DWT process.
The job is a Skip Delivery jobs and therefore has no weight - the reason being that the system has still applied a "Tip Outlet" to the job and is therefore expecting to see a weight
This is a known issue that is fixed in Weighsoft versions 5.544.14 and above. At that point skip "DEL" jobs are ignored by the DWT process.
"wasteItems[8].disposalOrRecoveryCodes[0].weight.amount" must be a positive number
Error 404 Waste input with ID xxxx not found
This error occurs when the message is sent to Defra but the ID number against the job is not recognised on their end.
If the Defra ID against the message appears to be valid but is not working you will need to contact Defra directly as the Id number for jobs are assigned by Defra when the first message is sent.
A common cause of this is on Weighbridge jobs where the "Defra id" box is exactly where the "Customer order No" box used to be.
This can often result in the weighbridge operator entering an incorrect number (or any character) in the Defra Id field which will then stop it from grabbing a valid number from Defra itself.
In order to fix this you will first need to delete the original defra message from the DWT screen (this will stop it from resending the same broken message). Then follow the below steps:
If the job has not yet been completed then you can correct this by just removing the erroneous entry and re-saving the job. That will generate a new Defra message and pull through a new number
If the job has been completed then you can edit the Transaction to remove the entry - saving the transaction will trigger a new message to be generated which will pull through a new number.
if the job has been completed and invoiced then you will need to contact the support team. The reason being that once an invoice has been generated you cannot remove the incorrect Defra id in the front-end of the application, the support team will have to remove it from the data for you. Once that is done you can go to the Transaction, enable the tickbox on the left, select Functions and click on the "resend to Defra" option. That will create a new DWT message and pull through a new Defra Id for the transaction.
"receiver.authorisationNumber" is not allowed to be empty
This refers to the "Waste Code" set against the receiving outlet used for the job.
It must be in the correct Waste Carrier Reg format.
"carrier.registrationNumber" is required
This refers to the "Waster Carrier Reg" set against the supplier used for the job.
iI must be in the correct Waste Carrier Reg format.
"carrier.registrationNumber" is required at the same time as "carrier.reasonForNoRegistrationNumber should only be provided when carrier.registrationNumber is not provided"
If a supplier does not have a Carrier Reg then a "reason" for that must be set in Weighsoft to allow for it.
However in these instances the messages are being rejected by Defra with the above error messages.
This is happening because when the Carrier Reg field is left blank it is not being sent to Defra at all, so the system rejects it.
But at the same time it is expecting to see a "blank" field in order to allow the "reason" to be accepted.
This is a known issue that is fixed in Weighsoft versions 5.544.13 and above. After that version, the system will send a "blank" value for the Carrier Reg number which will allow the "reason" field to be accepted
"The submitting organisation does not match the organisation that created the original waste item record"
This error occurs if the first version of a message was created using the Test API details, and it is now being resent using the Live details.
When a message is sent it is given a "Defra ID" that is specific to that job AND the test or Live area.
If you get this error please contact support as the fix is to remove the existing Defra ID from the message in the background. once that is done the message can be resent and it will pick up a new Defra Id to be processed.








