I’ve set up a login with Outseta and generated a unique token that I’m passing through the URL, for example:
However, when I land on the WeWeb page (production mode), the URL parameter isn’t being captured in my query variable.
Initially, I suspected the page was loading too quickly, so I added a 10-second delay but the issue persists. I’m not sure what else could be causing this.
“Are you preserving the variable on navigation” I thought it could have been the issue indeed but not I have edited it, republished, deleted caches and still the same issue.
@Roberto, the issue might be that the page is loading before the URL parameter gets added, so the query variable isn’t being captured. Have you encountered this timing issue before?
Initially, I suspected the page was loading too quickly, so I added a 10-second delay but the issue persists. I’m not sure what else could be causing this.
I only see a delay in the true path, in which you then navigate to home. In your recording at 1:05, I see you login > the access_token query parameter is visible in the URL > you redirect to post-login with the query parameter > then redirects to company/dashboard > then redirects once again to home. I don’t know the difference between dashboard and home but clearly your query parameter is falling off at this stage. I think what @Broberto was pointing to is in the “navigate to home” action, you do not add the query to the queries property.
** Not sure what you’re highlighting in the false path. My understanding is that is if the access_token in the URL query parameter is less than 3 characters, which is not the case for both logins you recorded.
