
EddieM.66666 (Customer) asked a question.
I have 40+ Identity Providers. I have routing rules set up for each IdP. Beginning yesterday (09 Feb 2026), I cannot Activate or Deactivate any of the routing rules. Network inspection shows a 500 error when I try to activate or deactivate a routing rule, but not much else.
Any pointers would be appreciated.

Hello @EddieM.66666 (Customer) Thank you for posting on our Community page!
I know there is a set limit to the amount of routing rules you can have, but that is around 200 or 250 so having 40+ should not be the issue.
500 error is a relatively general error and it does not say much, have you tried in an Incognito window? Maybe a cache issue could be the cause of the error.
If the cache is not the issue, I would recommend to check the System log and see if that shows something:
Go to Reports > System Log, Look for the "Update Policy" event. Even if the UI shows a 500, the System Log often captures the actual reason (e.g., ValidationError: Duplicate rule priority).
If this is not captured by the system log as well, the I would recommend to Open a case with Support for additional investigation.
Thank you for reaching out to our Community and have a great day!
--
Help others in the community by liking or hitting Select as Best if this response helped you.
Hi Paul,
Yeah, that 500 code was not very helpful.
I have tried managing these routing rules across 7 different browsers on Windows and MacOS. 14 when you count using incognito mode.
The System Log is not recording any details when I try to (De)Activate a routing rule. I see changes, but nothing related to (de)activate failures.
Is there any insight you can provide regarding routing rule priority? I am using one of two different criteria for routing rules: domain list on login, and user attribute matches a regex. I read in the docs that this (de)activate failure could be related to a priority conflict, but did not find anything specific to what the priority of routing rules needed to be.
Hi @EddieM.66666 (Customer) This would require a deeper dive into back-end logs, which from the Community side we do not have. The best corse of action here would be to open a Case with Support and they should provide a better assistance with this issue.
Thank you for reaching out to our Community and have a great day!
--
Help others in the community by liking or hitting Select as Best if this response helped you.