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.
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.
Failed Reason: "wasteItems[0].physicalForm" must be one of [Gas, Liquid, Solid, Powder, Sludge, Mixed]
This relates to the Digital Waste Tracking message referring to the Physical Form of the waste set against a Transaction item rather than the "State" that is set against the product in Lookups>Products.
This is a known issue that is fixed in Weighsoft versions 5.544.6 and above. After that version 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
"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.
Scenario 2 is a known issue that is fixed in Weighsoft versions 5.544.12 and above.
After that version any items flagged as "Bulky" and with the "EACH" unit of sale are ignored for DWT messages.
"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 nor recognised on their end.
In this instance you will need to contact Defra directly as the Id number for jobs are assigned by Defra when the first message is sent.
"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