FatTail incident

Users may receive traffic error when applying changes to existing lines that contain both a start date & time in GAM

Notice Resolved View vendor source →

FatTail experienced a notice incident on May 23, 2022 affecting AdBook+ Order Management, lasting 1d 17h. The incident has been resolved; the full update timeline is below.

Started
May 23, 2022, 11:18 PM UTC
Resolved
May 25, 2022, 05:13 PM UTC
Duration
1d 17h
Detected by Pingoru
May 23, 2022, 11:18 PM UTC

Affected components

AdBook+ Order Management

Update timeline

  1. identified May 23, 2022, 11:18 PM UTC

    We have identified an issue where on re-traffic (pushing changes to existing mapped GAM lines from AdBook), users are receiving a [LineItemError.ALREADY_STARTED @ lineItem[0].startDateTime] error. This error is incorrectly surfacing when re-trafficking existing line items that were: a) initially trafficked with a same day start date/time and b) do not have AdBook ad server date range applied to match the start date/time that was created in GAM. The incident was caused by an unexpected change to validation of ad server start dates/times, which was included in the release of v3.60.01 deployed to AdBook+ production sites on Friday, May 20th. To work around the issue and successfully traffic, users can enable ‘Ad Server Date Range’ and set the line item start date and time to match that of the associated GAM line item. We are testing a fix for the issue and plan to release this update on the evening of Tuesday, May 24th. Please contact us at support.fattail.com for questions or concerns. FatTail Support

  2. resolved May 25, 2022, 05:13 PM UTC

    This incident was resolved with the release of 3.60.02 on May 24th, 2022.