Tickets to Resolve

When a scale ticket fails to make it into BulkSource – because a file import failed validation, or because an automated plant integration could not sync it – that failure now lands in a persistent Tickets to Resolve list instead of going unnoticed. You can see why each ticket failed, fix it, and confirm it has been accepted.

This matters most for automated integrations, which previously failed silently with no error surface at all.

Where to find it

• Material Sales → Scale Tickets → the Tickets to Resolve tab, next to Posted Scale Tickets.
• Task Hub → the Tickets to Resolve tab, alongside the existing General tab.

Both tabs show the same list and behave identically. Use whichever fits your workflow.

What appears in the list

Any ticket that failed to persist in BulkSource and has not since been received successfully.

Failure type	Appears here?	Why
A file import where one or more tickets failed validation	Yes	Previously visible only as a Task Hub error file. This gives you a persistent view that lasts until the error is resolved.
An automated integration that could not sync a ticket	Yes	These used to fail silently with no error surface. This is the highest-value case for the tab.
A ticket you tried to post in the Scale House module that was rejected	No	These are handled in real time – you fix the problem and post again. They never appear here.

Columns

The list shows a selection checkbox, then:

Column	Meaning
External ID	The ticket's identifier from the source system. Click it to open the ticket for editing.
Source	Where the ticket came from – for example a file import or a named integration.
Error reason	The specific validation or integration error that caused the failure.
First failed at	When the ticket first failed.
Last retried at	When the most recent attempt was made.
Status	Unresolved or Resolved.

The list opens showing unresolved tickets only. A filter lets you switch to resolved tickets, which carry a Resolved indicator.

How a ticket gets resolved

Failures are tracked by External ID together with Source. A ticket counts as resolved once a record with that matching External ID and Source is successfully accepted into BulkSource – whether that happens because you fixed it here, or because a later import or integration run brought it in cleanly.

Resolve several tickets at once

1. Filter the list to Unresolved.
2. Tick the checkbox on each ticket you want to resolve.
3. Click Resolve. The action applies only to the rows you selected, not to everything visible.

Use this when the underlying problem has already been dealt with and the records simply need clearing.

Resolve one ticket in detail

Click the External ID to open a single ticket edit screen that works like the Scale House module.

• Unresolved tickets open directly in editable mode, with the fields that caused the validation errors clearly highlighted.
• All ticket fields remain editable, as in the Scale House module. Location and Scale are available as editable dropdowns during resolution.
• Ticket Status and Ticket Custom ID cannot be changed.
• On an unresolved ticket the actions are Resolve & Save and Back. On a resolved ticket they are Save and Back.
• Resolved tickets stay editable and keep opening this same screen until the ticket has been invoiced.

Fix a batch in Excel instead

If you would rather work outside the app, use Download Tickets to Resolve at the top of the tab.

1. Download the list. It includes every currently unresolved ticket, respecting any filters you have applied.
2. Correct the relevant fields in Excel. The file is in the standard ticket import format with one extra column appended – the error reason for each row – so no reformatting is needed.
3. Import the file through the standard ticket import flow.
4. Records that are accepted resolve their matching failure entries automatically through the same External ID reconciliation. There is nothing extra to click.

Note  The error reason column is there for your reference only. It is labelled so it will not be imported by mistake, and the import process ignores it, so you do not have to remove it before importing.

Access

Visibility is controlled by a dedicated Tickets to Resolve permission, assigned in User Management. It governs the tab in both places it appears – the Posted Scale Tickets page and Task Hub.

Not included in this release

• Automatic retries of failed tickets.
• Retry scheduling.
• Automatic resolution without a successful import or integration.
• Tickets originating from the Scale House Desktop App. Routing those failures into this same list is planned for a later release.

Only the latest state of each failure is kept, per External ID and Source, so the list stays a picture of what still needs attention rather than a growing history of every attempt.