I’m experiencing a strange behavior when sending some data to Xano. Let me explain the situation:
I have a workflow that is activated every time a user clicks a button after logging in. This workflow contains a request that was sending to Xano the hardcoded value “5” every time that happened.
I changed that hardcoded value for some value that is dependent on the user and deployed the update.
For every user, this works well since I deployed the change. But I have one single user that is still sending the previous hardcoded value “5”.
This is the only user that is creating this error. All others are working fine.
I have deployed a couple of updates of the app already. My guess is that the user is somehow still working with the previous deployment, but since this workflow is only activated after the person logs in… it means that the person has logged in several time to the previous version of the app, within a week since it was deployed (three times actually).
Does this sound feasible to you? Is there any way of preventing that from happening?
That’s not possible, I only shared the production link with the client, and also it’s not possible that the value is coming from Xano because the field was created together with the change and is 0 for all users - I already checked that to make sure that there are no errors there.
It’s very strange also because it’s the only user affected, all other users are working appropriately. It logged in today again and the issue persisted. If I check the Request log on the Xano side, everything looks similar to other users. The only difference is that input value that is 5 instead of 0.
Any clues of what I can look at to see if I’m missing something? I want to check all the possibilities before contacting the user. I have hardcoded Xano to make sure that the value that is stored is 0 no matter what comes, so right now it’s not creating an issue to the end user, but I know something is wrong.
I’m completely sure it’s only this user because I’m triggering an alert to my email every time that value is different from 0 - and it only happens with this user. Super strange…
It looks like the problem has been resolved - but I still don’t know how. The last deployment of the app was on Nov 5th, I haven’t deployed any changes since that.
The user errored the last time on 11/11. Since then, the user has logged in a couple of times (one on 12/11 and another one on 13/11) and the values were correct.
I’d love to understand what might have happened here in case I need to establish any firewalls on these type of changes in future deployments. I think it’s something worth looking at but not sure if there’s anything else I can do from my side.