Order Management
Orders in 'Fulfillment Error'
Incident Resolved: CTIM-776
A fix is in place for this issue, though some orders that were created before the fix and injected today had to be remediated. No more stuck orders have been found and the incident is now contained.
Please contact CTIM or see ticket for more details.
Incident Updated: The fulfiller has reported additional affected orders. Support teams are already reviewing the issue again.
Incident Updated: Reopening this issue since a workaround is in place but the primary cause remains on the website, pending action/acknowledgement from BoxUp devs.
Incident Resolved: CTIM-776
No additional stuck orders have been reported. Incident is now contained.
Please contact CTIM or see ticket for more details.
Incident Updated: The affected orders failed injection to MCP (upstream of paperless system). eCommerce support were able to help inject the orders after finding the ‘shippingAddressPerLineItemV2’ field was empty. Will continue to monitor before closing the issue.
New Incident: CTIM-776
Priority: High
Escalation sent to: Fulfillment: D’Ninjas for review.
BoxUp is currently seeing orders going into ‘Fulfillment Error’ state: 1046126, 1046127, 1046141, 1046133, 1046136.
We’re unable to see where in the process these items are getting stuck, but only notified once they been in this status for >1hour and shown in their reports.