March 11Mar 11 When querying the array state through the GraphQL API (array { state } and vars { mdState, startArray }), the response always returns "state": "STARTED", "mdState": "STARTED", and "startArray": true - even when the array is actually stopped. This makes it impossible for third-party clients (like the app i'm developing) to determine the real array state programmatically. The webGUI correctly shows the array as stopped, so the underlying system knows the state - it's just not being exposed through the GraphQL layer. This affects any app or integration that needs to conditionally disable features (Docker, VMs, Shares) when the array is down, or display the correct array status on a dashboard. Tested on Unraid 7.2.4, Unraid API 4.29.2+c39b0b26
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.