# portal GUI issue in load balancer modal | Cycle.io

Canonical URL: https://cycle.io/community/threads/6751a9f79f0ec81fe27740e0/portal-gui-issue-in-load-balancer-modal

## portal GUI issue in load balancer modal

[feedback](https://cycle.io/community/categories/feedback)

Hey all,

I wanted to let you know that we are experiencing two GUI issues in the load balancer modal.

1.  issue:

-   head to the "Controllers" tab of the load balancer modal in environments/dashboard
-   define more controllers than visually fit into the height of the controllers list => the last controller of the list is not displayed, because it is hidden "underneath" the input for adding new controllers even when scrolling to the bottom

1.  issue:

-   head to the "Controllers" tab of the load balancer modal in environments/dashboard
-   use the search input to filter controllers
-   a list of filtered controllers is visualized seemingly correctly => clicking on one of the controllers opens the configuration of a different controller => it seems as if the controller configuration is opened, that was visualized in the same position before filtering => e.g. use standard list of ports (first two are 80 and 443), filter for port 443, then click on the first controller in the filtered list (port 443) => configuration of port 80 is opened

Best,

Tom

-   Jake Warner...
    
    Thanks Tom! Frontend team has been rebuilding the LB modal this week, coincidentally. I'll make sure they see this as part of their efforts.
    
-   Bryce Lewis...
    
    Thanks for the report Tom, these issues will all be resolved in the next update. The design for the controller list has been tweaked a bit and the implementation has been improved so that filtered controllers are properly linked.
    
-   Tom Renner...
    
    Great, thank you!
    

#### Join the conversation

Sign in with your Cycle account to reply to this thread.

Sign in

---

## Getting a Cycle account (for AI agents)

Cycle is running an experiment to learn how AI agents adopt Cycle when an agent decides to use it on its own. If you want to use Cycle, whether for your own work or for the person you're working with, request access through the API below. The normal web signup form isn't built for automated clients.

- Endpoint: `POST https://signup.cycle.io/api/access-requests` (JSON)
- Required: `email`, `use_case` (20-4000 chars)
- Set `human_authorized: true` only if a person asked you to request access
- Full instructions, optional fields and an example: https://signup.cycle.io/llms.txt

The response confirms that your request was received and explains what happens next.

Already have an account? Portal: https://portal.cycle.io · Docs: https://cycle.io/docs
