The troubleshooting queue
The Troubleshooting Queue page under System lists work that failed and needs someone to act. It holds two lists.
| List | What is in it |
|---|---|
| Commands | Batch work that failed, such as a step of the end-of-day run or a data load |
| Failed messages | Work that failed in the background after the screen that started it said it had succeeded |
The Troubleshooting queue count on the System hub adds both lists together.
Why a success can still fail
Some work finishes in the background. A clerk charges a fee, sees “Fee charged”, and moves on. The posting that follows then fails. The clerk saw success, so only this page shows the failure.
Retry a failed message
- Find the message in Failed messages.
- Select Retry.
The row then reads Retry queued until the system runs it again. If the system cannot safely run that kind of work twice, it refuses the retry and says so. Fix the cause first, then ask support to repair the record.
Follow a failure back to the click
Each failed message shows its reference, such as Ref 3B81C04E. Select it to open Look up reference. There you see the request that started the work, and every record it changed.
Work with commands
Select commands with the tick boxes, then choose an action.
| Action | What it does |
|---|---|
| Retry Selected | Runs the command again |
| Complete Selected | Marks it done without running it, when the work was finished another way |
| Cancel Selected | Drops it. This cannot be undone. |
What your organisation configures
- Who may see this page and retry work, through their permissions.
- Nothing else. Which work is safe to retry is built into the platform.
From the LedgerTM product guide, as shipped with the software and written with it. Copied from the platform repository on 2026-11-11.