gridX's System Status

Updates

• Sep 17, 2026 2:34 PM CEST

  Impact

  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.

  Root Cause

  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.

  Detection

  The issue was surfaced through support requests reporting that affected users could no longer trigger gateway scans.

  Resolution

  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