Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: Himalaya
-
Fix Version/s: Himalaya
-
Component/s: None
-
Labels:None
-
Environment:
Sapi – Build 735
Reseller UI – Build 178
Data Util Jar – Build 126
Ops Scripts – build 230
Core – Himalaya Build 2
BidMgr – Himalaya Build 11
-
Story Points:3
-
Sprint:Sprint 4
Description
If the user edits an order with a deprecated BA or copies an archived order with a deprecated BA and then requests deployment, the order goes to the ERROR state immediately.
I cannot find anything in the AML, core or listener log indicating what actually happened.
To reproduce, create an order and deploy it. Once deployed, edit the BA and mark it as deprecated. Next, edit the order (add a comment or something) and click request deployment. Notice the order goes to error and the user gets a notification to log a ticket with tech ops and gives them the merchant and order IDs.
