Last Thursday we noted that ‘AEMO declares ‘Scheduling Error’ in relation to glitches on Friday 10th April and Saturday 11th April 2026’.
What I should have noted at the time, but did not, was that the same update (i.e. on Friday 29th May 2026) the AEMO also declared Scheduling Errors (together anointed number 76), with respect to the joint glitches in November 2025:
| Around lunchtime,
on Thursday 6th November 2025 |
In the morning,
on Tuesday 11th November 2025 |
|---|---|
|
We saw this unfold on the day, and progressively explored in articles here: … sharing some via social media
More articles followed, and we collated them here in relation to that incident (adding one more with this article). |
We saw this happening, and wrote about it via ‘Has it happened again … have gremlins invaded NEMDE and triggered a frequency excursion (Tuesday 11th November 2025)?’:
We’ve progressively collated a number of articles here in relation to that incident (adding one more with this article). |
The AEMO update was noted with Incident Number 76:
On 6/11/2025 there was an error in the VIC demand calculation caused by bad SCADA data flowing through due to a misconfiguration for a newly-modelled solar farm in Victoria. As a result, VIC Initial Demand (Initial Supply) was incorrectly calculated, leading to erroneous dispatch outcomes.
The issue was resolved within 15 minutes on the active EMS site on 6/11/2025, however, the fix was not applied to the passive site which led to a reoccurrence of the issue on 11/11/2025 when there was an EMS site switch. Overall, the error resulted in approximately 15,100 MW of erroneous demand calculations.
Be the first to comment on "‘Scheduling Error’ also declared in relation to glitch(es) on 6th and 11th November 2025"