Openbravo Issue Tracking System - Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0057652ModulesAdvanced Warehouse Operationspublic2025-01-15 17:242025-01-20 10:52
Reportermalsasua 
Assigned ToAtulOpenbravo 
PriorityhighSeveritymajorReproducibilityalways
StatusnewResolutionopen 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Regression date
Regression introduced by commit
Regression level
Review Assigned To
Support ticket
OBNetwork customer
Regression introduced in release
Summary0057652: Push API is sending DO in Ongoing status
DescriptionWhen a distribution order is created and completed from AWO app, an EDL Request is created using the event OBDOAPI_UpdateDOStatus , but sometimes, the record is sent in status OnGoing

It should not be possible because the DO are created in OnGoing status directly in the Frontend.

Analyzing the code, we have seen the event only is triggered when the DO is processed, but we have some cases that the json sent from EDL Request contains docStatus=OnGoing
Steps To Reproduce. it happens randomly
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2025-01-15 17:24malsasuaNew Issue
2025-01-15 17:24malsasuaAssigned To => Triage Omni WMS
2025-01-15 17:27vmromanosDescription Updatedbug_revision_view_page.php?rev_id=29056#r29056
2025-01-15 17:37vmromanosNote Added: 0174198
2025-01-20 10:52mtaalAssigned ToTriage Omni WMS => AtulOpenbravo

Notes
(0174198)
vmromanos   
2025-01-15 17:37   
@Developer:

In theory the launch of this event is centralized in the UpdateDOStatusEvent AfterDistributionOrderProcessedHook class, which is executed only after processing the DO (and therefore changing its status). See ProcessDistributionOrderUtil.processDistributionOrder()

The ongoing status is not changed through this method, but instead the DO is synchronized directly with the Ongoing status. In theory this event shouldn't be launched for a DO in that status.

After a quick view to the code I don't find the root cause. My first idea was related to the asynchronous nature of the push API events. But this shouldn't be a problem in this concrete case because the DO sent is in ongoing status, which shouldn't be possible from the application as explained above.
The only possibility I see is that someone has changed the status back to ongoing after processing the DO, which is something impossible from the UI, and very weird from the user perspective.


Because of that my recommendation would be to add log in the UpdateDOStatusEvent to print the stack trace and the DO information when we detect the DOi is in ongoing status to try to understand the root cause if we are unable to reproduce it ourselves.