Drieam - Notice history

We’re pleased to confirm that the technical issue impacting Eduframe has been fully resolved, and the system is operating normally.

As previously communicated, the impact of this issue was very limited, affecting only 0.23% of all events sent during the affected period. We’ve successfully completed all checks on missed events.

We apologise for any inconvenience this may have caused. If you have any additional concerns or questions regarding this issue, or believe any specific events might have been missed as a result of this bug, please don’t hesitate to contact us at support@drieam.com.

We’re providing an update on the bug that has been causing events in Eduframe not being handled. We want to start by confirming that the impact has been very limited, affecting 0.23% of all events sent during the affected period, most of which have been handled by now.

Here’s what has been accomplished so far:

• All delayed emails have now been sent, with the exception of those awaiting specific input from the affected customers (who will be contacted personally today).

• All missed course and program enrollments have been successfully created.

• Teacher & student enrollments that were retroactively created have been synced to Canvas.

Our team is continuing to work diligently on the remaining checks. We estimate that 50% of these checks are complete. The current estimate to finalize everything is tomorrow afternoon. We appreciate your patience and understanding as we work to fully resolve this matter.

This incident has been resolved.

Since the fixes of early this morning, all background tasks are running smoothly and stable again. Our cloud hosting partner Heroku and SalesForce are implementing measures to prevent this from happening again.

The Heroku and SalesForce team are working on a solution to mitigate the issue. The situation can be monitored on SalesForce's Trust Portal.

Next update before: Tue 11 June 8.00 CEST.

Unfortunately, Heroku has not been able to implement a fix for this issue. We'll keep monitoring the situation.

Next update before: 19.00 CEST.

We have identified the cause of a number of issues in Portflow at the moment.

Our cloud hosting provider Heroku is experiencing outages which are causing background jobs that Portflow relies on to not complete. This may cause issues with snapshots not being finished, notifications not being sent or templates not being imported. We're closely monitoring the situation and will update you before 17.00 CEST.