API Redirect Rules
I 'm setting up a redirect rule so that if my API response status is not 200 , it should redirect to the Home page . The API has both auto -fetching and server -side fetching enabled . The issue is that , even when the API returns a 200 status (meaning it shouldn 't redirect ) , the rule is ignoring this condition and redirecting to Home constantly . I also tested using "is server , " but the redirection still happens without respecting the established logic . Does anyone know if this could be a bug , or am I doing something wrong in the implementation ? @Andreas Møller Andreas , I believe I ’ve identified the issue . To obtain the user ’s authentication token , I ’m retrieving the store _id from localStorage . However , for some reason , this information isn ’t being fetched correctly , resulting in an "unauthenticated user " error . Could this limitation be related to server -side processing ? Could you store it in a cookie instead with the set session cookie action ? I 'm using the access token to check if the user is logged in , and my backend is Xano . So far , everything is working correctly . The issue is that , since this is a SaaS , a user can have an account in Store A or Store B . I save the store _id in local storage , and in all API requests , I pass the store _id to retrieve the necessary information . For the user , I also need to retrieve their data by providing the store _id to check if they are logged into Store X or Y . The problem is that , when using redirect rules , I 'm unable to obtain the store _id . I 'm not sure how to use cookies (or if it 's even possible ) to store the store _id and access it on the server side , or if there is another way to solve this issue . Otherwise , this functionality , which I find amazing , unfortunately won 't work for me . Is there any way to work around this problem ? now it worked perfectly
