Skip to content

Incidents and notifications

The incidents and notifications of Fluvius Fall-Back Flex in the Voltmasters platform: when the controller raises them and what to do, plus the reminder mails for the planning certificate.

The controller raises an incident when an activation cannot be executed as it should. Incidents appear under Incidents in the project and are sent to the project members who receive notifications. An incident closes itself once the cause is gone.

Fall-Back Flex

IncidentWhenWhat to do
Fall-Back Flex limit not reached within the response deadlineThe net consumption is still above the limit after the 3-minute response time. Critical.Check which devices are held back on the Fall-Back Flex page and whether they follow their setpoint.
Fall-Back Flex has no flexibility left while consumption still exceeds the limitEvery flexible device is held back and the site is still above the target. Warning.Add flexible consumption, or check that the devices have the right nominal power.
Fall-Back Flex limit in force without a usable grid measurementA limit applies but the grid meter gives no usable value. The controller keeps the devices where they are. Critical.Check the grid meter and its connection.
Fall-Back Flex is enabled but no contractual consumption power is configuredP_base is missing, so a percentage cannot be converted into kW. Visible to Voltmasters only.Enter the access power in the grid settings.

The first and the third incident also send an immediate push notification in the Voltmasters app and alert Voltmasters support.

Day-ahead planning

IncidentWhenWhat to do
Fluvius planning API unreachableFive polls in a row failed.Check the internet connection of the controller. The last plan stays in force.
Fluvius planning API certificate refused or unusableFluvius refuses the certificate, or the key or file cannot be used.Check that Fluvius linked the certificate to the right asset point id, and that the key matches. See troubleshooting.
Fluvius planning API certificate expiredThe certificate has expired.Upload the renewed certificate.
Day-ahead plan version from Fluvius rejectedA new plan version could not be read. The previous version stays in force.Contact Voltmasters support.
Read receipt of the day-ahead plan could not be delivered to FluviusThe read receipt still failed after all retries.Check the internet connection. Contact Voltmasters support if it returns.
Day-ahead planning program without a configured reference powerFluvius sent a program that is not mapped, and there is no default.Add the program id with its reference power in the settings.

All planning incidents are critical, except the unmapped program (warning). They do not send a push notification.

The RTU link itself has its own incident when it drops. See Fluvius.

Certificate reminders

With day-ahead planning, the platform mails the project members who receive incident mails before the certificate expires: 60, 30, 15, 7 and 1 day before, and on the expiry day. The mail explains the three steps (order, register with Fluvius, upload). Uploading a new certificate restarts the reminders.

Fluvius only accepts a replacement certificate between 90 and 15 days before the expiry date. Act on the 60-day mail.