F5 Starts Returning 302

While making some routine changes to security policies on our F5 (taking attack signatures out of staging, adding a policy to some new virtual servers), many of our systems went off line with all the URLs returning a 302, which seemed to overload the system.

I am familiar with security policies in the ASM, but not familiar with the inner workings of the F5 overall. What are the scenarios that would cause the F5 to start returning 302 for requests that were not even affected by security policy changes? Is this a default behavior of the F5 if the system becomes too busy to process requests? Any information or help would be appreciated.