@PatrickC8660 Yes, the IDS URL for Cisco Finesse can support load balancing to improve reliability and eliminate the single point of failure you’re experiencing. You can set up a load balancer that directs traffic to multiple IDS servers instead of pointing the IDS URL to just one server. To do this, configure a load balancer (like HAProxy or a hardware option) with all your IDS servers behind it and update the IDS URL in your Cisco Finesse and Pega configurations to use the load balancer’s address. Regarding session persistence, it’s important to determine if your IDS requires each user session to stay connected to the same server. If the IDS needs persistent sessions, configure the load balancer to use sticky sessions so that all requests from a single session go to the same IDS server. However, if the IDS can handle sessions across different servers without issues, you might not need to enforce session persistence. It’s best to check Cisco Finesse’s documentation or consult with their support to understand how your specific setup handles sessions and to ensure that load balancing won’t disrupt your SSO configuration. Implementing load balancing should enhance your system’s resilience and scalability while maintaining seamless connectivity for your users.