Bin Inspection Task Stuck in IN PROGRESS

 Bin Inspection Task Stuck in IN PROGRESS

Site: Bleckmann (Patagonia) – Roosendaal

Problem Statement  The client is unable to process a bin inspection for a specific bin.

• All other bin inspections complete successfully.

• One specific bin does not arrive at the inspection port.

• Call Specific Bin has been attempted, but the bin still does not appear.

• The inspection task remains in IN PROGRESS status.

Root Cause  This issue occurs when multiple dashboard tabs are opened for the same inspection port.

• The bin arrives at the inspection port.

• One of the open tabs receives the event.

• The bin leaves the port without being inspected.

• The inspection task remains stuck in IN PROGRESS, preventing further inspection requests.

Resolution Steps

1. Identify the Inspection Task

   • Open the inspection dashboard and note REFERENCE_VALUE and REFERENCE_TYPE.

   • Example: REFERENCE_VALUE: 12302, REFERENCE_TYPE: CONTAINER_LOCK.

2. Verify the Task in Database

   • Run: SELECT * FROM inspection_task WHERE reference = 'REFERENCE_VALUE' AND reference_type = 'REFERENCE_TYPE';

   • Verify that the task is correct and status is IN PROGRESS.

   • Do not execute UPDATE without Dev team approval.

3. Cancel the Stuck Inspection Task (After Dev Approval)

   • Run: UPDATE inspection_task SET status = 'CANCELLED' WHERE reference = 'REFERENCE_VALUE' AND reference_type = 'REFERENCE_TYPE';

   • Example: UPDATE inspection_task SET status = 'CANCELLED' WHERE reference = '12302' AND reference_type = 'CONTAINER_LOCK';

4. Verify

   • Confirm task status has changed to CANCELLED.

   • Ask client to initiate bin inspection again if required.

Expected Result

• The stuck inspection task is cancelled successfully.

• Client can create a new bin inspection request.

• Bin is called to the inspection port and inspection proceeds normally.

Prevention

• Ensure only one dashboard tab/window is open for a particular inspection port.

• Avoid opening multiple sessions for the same port simultaneously, as this can cause the inspection event to be consumed by another tab, leaving the inspection task stuck in IN PROGRESS.

Root Cause Summary  Cause: Multiple dashboard tabs were opened for the same inspection port. The bin arrived but was not inspected because the event was consumed by another open session. The inspection task remained in IN PROGRESS and required manual cancellation from the database after Dev team approval.