Overview
This guide outlines how to identify deleted or failed transactions, interpret common error messages, and regenerate transactions based on job type. It also explains how to resolve issues using the Exceptions screen and Admin Functions.
1. Identifying Deleted Transactions
Before further investigating and possibly regenerating transactions, you should first search for deleted transactions in case it has been deleted without your knowledge.
Steps to Search for Deleted Transactions
Hover over Administration, then click Transactions.
Click the Funnel icon in the top left.
If using Version 1 of the Transactions screen press Search
Change the Show Deleted drop-down to Show, then click Search.
Note: If the transaction appears, it has been deleted.
To restore it:
Click Edit next to the ticket number.
Un-check Deleted.
Click Save.
2. Using the Exceptions Screen
If no deleted transactions are found, check the Exceptions screen:
Click the Burger Menu (three green bars) in the top right of the screen.
Go to Exceptions.
Information Displayed for Each Exception
Event Timestamp: Time of the event (if recorded).
Transaction Timestamp: Time the system attempted to create the transaction.
Look Up Id: Internal job ID.
Event Type: Type of job (e.g., skip, material).
Exception: Reason the transaction failed.
Notes: Ticket number.
Company Code: Company (for multi-company setups).
Resolved: Always shows a cross (❌).
Note: The (❌) is to be pressed once the transaction has been regenerated after following the steps later on in this article.
3. Common Error Messages and Their Meaning
String or Binary Will Be Truncated
Cause: This error indicates an item on the account, order or job is too long.
Fix: Check for unusually long entries in the order and job:
Phone contact fields (e.g., multiple numbers).
External Reference 1 (limit: 50 characters).
Object Reference Not Set to an Instance of an Object
Cause: Missing required data.
Fix: Check the following:
Account has a primary address.
Order and job have account and address set.
Product, waste type, or container are correctly assigned.
Execution Timeout Expired
Cause: Performance issue.
Fix: No investigation needed—proceed to regenerate.
4. Regenerating Transactions by Job Type
Skips, Materials, RMC, Hazardous
Click Administration > Admin Functions.
Under Reset to Active, enter the job number in Enter Ticket No.
Click Find, then Reset to Active.
Go to the Outstanding Tickets screen for the job type and complete the job.
Weighbridge
Click Administration > Admin Functions.
Click Transaction.
Enter the date range in Generate Missing Weighbridge Transactions.
Click Generate.
Trade
Click Administration > System Settings.
Click Functions, then go to the Other tab.
Enter the round dates in Generate Missing Coll Transactions.
Click Generate Missing Collection Transactions.
Trade Overweight
Click Administration > Admin Functions.
Click Trade.
Under Generate Trade Surcharges:
Enter the date range or
Enter the Collection Id for a single collection.
Click Complete.
Still Unable to Generate?
If you're still unable to generate the transaction please raise a case with support quoting the title of this article along with the ticket numbers, ticket type and the error given.