ShipHawk incident

Investigating reported issue with warehouse filtering in the User Interface

Minor Resolved View vendor source →

ShipHawk experienced a minor incident on March 10, 2022 affecting TMS, lasting 59m. The incident has been resolved; the full update timeline is below.

Started
Mar 10, 2022, 04:18 PM UTC
Resolved
Mar 10, 2022, 05:17 PM UTC
Duration
59m
Detected by Pingoru
Mar 10, 2022, 04:18 PM UTC

Affected components

TMS

Update timeline

  1. investigating Mar 10, 2022, 04:18 PM UTC

    We are currently investigating an issue with warehouse filtering in the user interface.

  2. identified Mar 10, 2022, 04:44 PM UTC

    Status update: The issue has been identified. A solution has been identified, and we are deploying the fix now. Customer Impact: Some Users with more than one warehouse assigned to them cannot see/filter orders for the warehouses they are assigned to.

  3. resolved Mar 10, 2022, 05:17 PM UTC

    Status update: A fix has been deployed and confirmed to be working as expected. Customer Impact: Some Users with more than one warehouse assigned to them cannot see/filter orders for the warehouses they are assigned to. Start Time: March 10, 6:27 AM PST End Time: March 10, 8:53 AM PST