The issue has been resolved and the backlog has been processed.
Posted May 19, 2022 - 10:49 PDT
Update
A fix to facilitate the required configuration for faster processing is still being tested in the lower environment. Technical teams will continue to monitor the change tonight before implementing it in production. The next update will be posted tomorrow, 05/19/2022.
Posted May 18, 2022 - 13:27 PDT
Update
Technical teams continued to work on a fix last night and have formulated a plan that is currently being tested for implementation in the production environment.
Posted May 18, 2022 - 04:54 PDT
Update
We have been monitoring the progress of the backlog processing and are still noticing delays. Technical teams will continue to work offline tonight to work on a required change in the environment, following which the next update will be provided tomorrow morning, 05/18/22.
Posted May 17, 2022 - 14:51 PDT
Update
Technical teams are reviewing the required code change to facilitate the desired scaling.
Posted May 17, 2022 - 11:35 PDT
Update
The backlog processing is still in progress, however, there is no significant reduction in the lag time. We are looking into a code change to facilitate the scaling that is needed to process faster.
Posted May 17, 2022 - 10:03 PDT
Update
The backlog processing is still ongoing as we continue to monitor the progress.
Posted May 17, 2022 - 08:25 PDT
Update
The backlog processing is still ongoing. Technical teams are also working on scaling up the service to enable data processing in real-time.
Posted May 17, 2022 - 07:07 PDT
Update
The backlog processing is still in progress. Technical teams are continuing to monitor the progress.
Posted May 17, 2022 - 05:33 PDT
Identified
The impacted service has been restored, and the backlog processing is currently in progress.
Posted May 17, 2022 - 03:55 PDT
Update
The issue has been identified and a fix is being implemented.
Posted May 17, 2022 - 03:42 PDT
Update
The investigation is currently underway and the technical teams continue to drill down to identify the contributing factor(s).
Posted May 17, 2022 - 02:29 PDT
Investigating
Incident Description: The US Customers may experience delays before inventory data is visible due to a processing backlog. Data may be up to 14 hours out of date.
Priority: 2
Restoration activity: Technical teams have been engaged and are currently investigating.
Posted May 17, 2022 - 01:16 PDT
This incident affected: Flexera One - IT Visibility - North America (IT Visibility US).