CartonCloud incident
Consignment items not creating on Consignments being generated from Sale Orders
CartonCloud experienced a minor incident on February 5, 2026 affecting Consignment Processing, lasting 4h 47m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Feb 05, 2026, 04:38 AM UTC
We are aware of an issue affecting some customers where Consignment items are not being created on Consignments which are generated from Sale Orders. We have identified the issue and are working toward a fix.
- monitoring Feb 05, 2026, 04:54 AM UTC
A fix has been implemented and Consignment items will now be created on Consignments generated from Sale Orders successfully. However, we suggest to check accuracy of Consignment Items on any Consignments created from approximately 2:45pm - 3:50pm AEDT February 5th and update accordingly. Alternatively, you can Delete the Consignment which has not generated items and re-generate it from the Sale Order > Consignment tab. We apologise for the inconvenience caused.
- monitoring Feb 05, 2026, 05:12 AM UTC
A fix has been implemented and Consignment items will now be created on Consignments generated from Sale Orders successfully. However, we suggest to check accuracy of Consignment Items on any Consignments created from approximately 2:45pm - 3:50pm AEDT February 5th and update accordingly. Alternatively, you can Delete the Consignment which has not generated items and re-generate it from the Sale Order > Consignment tab. We apologise for the inconvenience caused.
- monitoring Feb 05, 2026, 05:14 AM UTC
A fix has been implemented and Consignment items will now be created on Consignments generated from Sale Orders successfully. However, we suggest to check accuracy of Consignment Items on any Consignments created from approximately 2:45pm - 3:50pm AEDT February 5th and update accordingly. Alternatively, you can Delete the Consignment which has not generated items and re-generate it from within the Sale Order > Consignments tab. We apologise for the inconvenience caused.
- resolved Feb 05, 2026, 09:25 AM UTC
This incident has been resolved.