TravelBank incident

Expense OCR Issues

Resolved after 2 days 19 hours, affecting Expense Receipts, on April 19, 2024.

postmortem Apr 23, 2024, 09:57 PM UTC

This issue occurred due to changes related to how we are storing expense receipt images. The changes were tied to our 8.13.0 API release which was initially released on April 18th. The changes resulted in requests to our OCR provider being made before the receipts had completed uploading, resulting in OCR not functioning properly. Our regression testing in our preproduction environments did not catch this issue, but we are updating our automation tests to ensure that this issue will not occur again with future releases. With all releases, we do our best to identify and resolve any issues before we release, but from time to time issues will make it past our testing either due to variation between our production and preproduction environments or testing gaps. We use every incident/issue as learning opportunity to continuously improve. We apologize for the inconvenience this issue posed to some of our customers and will do our best to ensure it does not happen again.

Started
Apr 19, 2024, 09:33 PM UTC
Resolved
Apr 22, 2024, 05:30 PM UTC
Duration
2d 19h
Detected by Pingoru
Apr 19, 2024, 09:33 PM UTC

Affected components

Expense Receipts

Update timeline

  1. identified Apr 19, 2024, 09:33 PM UTC

    There is an issue at the moment related to expense OCR. Expense receipt attachments are not automatically being scanned. We are working on a fix for this and will provide an update as soon as it is released.

  2. resolved Apr 22, 2024, 05:30 PM UTC

    This issue has been resolved.

  3. postmortem Apr 23, 2024, 09:57 PM UTC

    This issue occurred due to changes related to how we are storing expense receipt images. The changes were tied to our 8.13.0 API release which was initially released on April 18th. The changes resulted in requests to our OCR provider being made before the receipts had completed uploading, resulting in OCR not functioning properly. Our regression testing in our preproduction environments did not catch this issue, but we are updating our automation tests to ensure that this issue will not occur again with future releases. With all releases, we do our best to identify and resolve any issues before we release, but from time to time issues will make it past our testing either due to variation between our production and preproduction environments or testing gaps. We use every incident/issue as learning opportunity to continuously improve. We apologize for the inconvenience this issue posed to some of our customers and will do our best to ensure it does not happen again.

Your product runs on more than TravelBank

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →