No incidents reported
Between September 9 and September 15, users in Xenon who had been granted a permission scoped specifically to gateway scan jobs (rather than the broader permission covering all gateway job types) were unable to trigger gateway scans. No other functionality was affected, and jobs already in progress continued to run normally.
Gateway scan, reset, and restart were previously triggered through three separate, job-type-specific endpoints. These were consolidated into a single endpoint, with the job type moved from the URL into the request body, to support a more REST-conformant design and to allow richer error responses when a job creation conflicts with an existing one.
The new endpoint required a different permission than the old ones it replaced. Users who only had one of the narrower permissions lost access after the switch.
The issue was surfaced through support requests reporting that affected users could no longer trigger gateway scans.
Once identified as a permission mismatch, the broader permission was granted to all groups that previously held any of the narrower, job-specific permissions, restoring the expected functionality.
This broadens what those groups can do: a group that could previously only trigger scans can now also trigger resets and restarts. This change is an interim measure and we're evaluating whether a consolidated or per job-type permission model is the right long-term design.
Resolved after 0m
The prices of the bidding zones have been backfilled, so optimization is stable again.
Resolved after 9h 1m
FoxESS inverters that were being curtailed during the time of a release on the 26th Aug. around 11:36 weren't able to correctly lift those limits causing suboptimal control.
Resolved after 0m
What happened: Between 16:42 and 07:38 CEST, charging control decisions for cloud connected EVs were temporarily not executed. Affected vehicles remained in their last known state for the duration of the incident.
Impact: Approximately 5% more charging sessions missed their target compared to baseline. The majority of charging sessions completed successfully. No data was lost, and all systems resumed normal operation automatically after the issue was resolved.
Resolution: A fix was deployed and normal operation was restored by 07:38 CEST on August 12.
Resolved after 0m
A scheduled maintenance window will take place on August, 3rd, from 08:30 to 09:30 CET. During this time, you may experience brief service disruptions.
The maintenance work has been completed successfully.
There won't be any interruptions or rejections for the Webhook Subscription API anymore.