Displayr Documents that use Custom Fonts are failing to load

This incident has been resolved with the completion of our rollback process.

We believe this issue is triggered when a company’s cloud drive contains duplicate custom font files, which can prevent affected Displayr documents from loading. Our rollback process is continuing.

We’ve identified the issue and are rolling back the current release, which we believe will restore normal loading for Displayr documents using custom fonts from the Displayr Cloud Drive. We’ll confirm once the rollback is complete and continue monitoring.

Rollback is estimated to be completed within the next 40 minutes.

Displayr Documents that make use of Custom Fonts from the Displayr Cloud Drive are currently failing to load with an error message that mentions "An item with the same key has already been added.".

We are currently investigating the issue and will post another update shortly.