User on cloudCode do not match real values

[nirco123]

Steps to reproduce:

1. Lets say that we have column in User called "Enable"
2. setup Enable=false
3. call cloudCode function from JS SDK -> change enable to Enable=True
4. call same cloudCode function (or any other) from JS SDK -> check request.user.Enable
5. you will get Enable=false instead of Enable=True

My question is: when a user call any CloudFunction from and SDK do the parse lib become the user each time and query for the latest values, meaning, can we say with confident that request.user is always up-to-date or should I become the user with session token on each call?

[aaronbannin]

Without seeing the code, it's hard to know exactly. Perhaps you're not calling the .save() method?

[drew-gross]

We have lots of passing test cases that cover these features. Can you post some code that reliably reproduces your issue? Ideally as a test case we can add to our test suite.

[flovilmart]

Closing due to lack of activity, please update to latest parse-server version and reopen if the issue persist.

Don't forget to include your current:

• node version
• npm version
• parse-server version
• any relevant logs (VERBOSE=1 will enable verbose logging)