Rec Refresh - Delayed Completion

Refresh attempts should complete at typical speeds at this time, and all previously queued Refreshes have been processed successfully!

If you observe any further delays or related errors with the Refresh, please don't hesitate to contact support@floqast.com for continued assistance.

We have identified the probable cause of the queue delay, and additional resources have been deployed to process outstanding Refresh requests. The original root cause is unrelated to the Refresh process, but shared database resources were being consumed and therefore delaying Refresh processing.

At this time, Refreshes should still be completing 100% but hopefully at an increased rate. We will continue to work on full remediation and update about a return to full-speed Refreshes.

We are continuing to investigate the issue causing Refreshes to complete slowly. At this time we can confirm that Refreshes are reaching 100% completion, but at a delayed rate. In addition to debugging the root cause, we are scaling up resources to help complete the existing queue since it is larger than normal due to accumulated prolonged Refreshes.

We are currently investigating reports of Refresh times being delayed. At this time it appears that refreshes are reaching 100% completion, but are proceeding at a rate slower than typically observed. Further updates will be posted here ASAP!

In the meantime, users are encouraged to let any pending Refreshes reach completion before retrying the Refresh (doubling/tripling/etc of attempts may cause organic concurrency delays with ERP and/or Storage Provider APIs)