Ambra experienced a minor incident on August 29, 2024 affecting Web Services and Image Processing and 1 more component, lasting 1h 52m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Aug 29, 2024, 04:07 PM UTC
We are aware of an issue which is causing dictionaries to revert to their previous values. Our engineering teams are investigating and we will provide updates as soon as possible.
- investigating Aug 29, 2024, 04:32 PM UTC
Our engineering teams have not yet identified the root cause. We are continuing to investigate and will provide further updates as soon as possible.
- investigating Aug 29, 2024, 05:26 PM UTC
Our engineering teams have not yet identified the root cause for the issue but we have identified a fix for those experiencing the issue where dictionaries are reverting to their previous values. Please contact our Support team by submitting a case via the Intelerad Service Portal or calling our Support line at (888) 315-0790, and we will help initiate this fix for you.
- resolved Aug 29, 2024, 06:00 PM UTC
Our engineering teams will continue on working towards a root cause for the issue and will provide it once available. At this time as we have identified a successful fix for customers experiencing the issue where dictionaries are reverting to their previous values. If you are experiencing this issue we ask that you please contact our Support team by submitting a case via the Intelerad Service Portal or calling our Support line at (888) 315-0790, and we will help initiate this fix for you.
- postmortem Dec 12, 2024, 11:07 PM UTC
Issue: Dictionaries were reverting to their previous values causing data issues on study data that required dictionary updates. Root Cause: In the previous release and a subsequent change control, a change was made to fix an issue where if the user's date format was not YYYY-MM-DD, date fields on the advanced search panel would fail to repopulate correctly after performing a search. When the fix was made, one of the side effects was that date fields being populated from the query string were changed from expecting a format in YYYY-MM-DD order \(with or without separators\) to one in the same order as the user's date format. Because the date of birth from the Epic link was in YYYYMMDD format, the advanced search form would interpret the date in the user's date format \(which is presumably MM-DD-YYYY\), resulting in the 19 or 20 at the start of the year being interpreted as an invalid month. The conversion would then fail, resulting in the date of birth field not being populated. Resolution: A fix was implemented to change the behavior so that if the conversion fails, we will instead populate the field with the date as it was originally passed in without attempting a format conversion.