We came across something similar on a forum where SAML was in use previously and was now disabled. However, the saml_slo_target_url was still configured and Discourse kept using it.
So the fix should be that that is only being used when the SAML plugin is enabled AND the user has originally logged in with SAML.