From a94ebcd1abda461eeb21f71eb5a0b326448d6629 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Ro=C3=ABl=20Gonzalez?=
 <13934159+roelgonzalez@users.noreply.github.com>
Date: Tue, 4 Aug 2020 16:05:35 +0200
Subject: [PATCH] Update universal-routes.blade.md (#66)

Add mention to disable this feature if you are implementing it in your custom onFail logic
---
 source/docs/v3/features/universal-routes.blade.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/source/docs/v3/features/universal-routes.blade.md b/source/docs/v3/features/universal-routes.blade.md
index 947a2ac..8169d3f 100644
--- a/source/docs/v3/features/universal-routes.blade.md
+++ b/source/docs/v3/features/universal-routes.blade.md
@@ -6,7 +6,7 @@ section: content
 
 # Universal Routes {#universal-routes}
 
-> Note: If you need custom [onFail]({{ $page->link('tenant-identification') }}) logic, you cannot use this feature as it will override any of your changes to that logic. Instead, look into the source code of this feature and make your onFail logic implement universal routes too.
+> Note: If you need custom [onFail]({{ $page->link('tenant-identification') }}) logic, you cannot use this feature as it will override any of your changes to that logic. Instead, look into the source code of this feature and make your onFail logic implement universal routes too. If you do this, make sure to disable this feature in the config file followed by a cache clear.
 
 Sometimes, you may want to use the exact same **route action** both in the central application and the tenant application. Note the emphasis on route **action** — you may use the same **path** with different actions in central & tenant routes, whereas this section covers using the same **route and action**.