messere1 opened a new issue, #1595: URL: https://github.com/apache/rocketmq-dashboard/issues/1595
## Problem `useInstanceFilter` is documented to keep instance-scoped pages usable when `listInstances()` fails, but its selected-ID calculation only accepts a route instance that is present in the loaded list: ```ts routeInstanceId && instances.some((instance) => instance.id === routeInstanceId) ``` When instance discovery rejects, `instances` remains empty and `/instance/<id>/topic`, Consumer, Message, ACL, DLQ, and Resource Plan pages all receive an empty `selectedInstanceId`. They then disable actions or skip their instance-scoped data requests even though the URL already contains a usable instance ID. ## Expected behavior - If instance discovery fails, preserve the instance ID from an instance-scoped route. - If discovery succeeds, continue validating the route ID and redirecting unknown IDs to the first available instance. - Static instance routes should continue selecting the first discovered instance. - Add focused hook tests for failed discovery and successful unknown-ID fallback. ## Scope Shared frontend instance-filter hook and tests only. ## Track Track 1 / Studio multi-instance navigation reliability. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
