It may be that I am using the wrong method to send variables to the server functions, but if I create execution with one value, and then again with a different value, the function fires with the original value and not the new one.
I have attached a screenshot of how I am getting the variables from the execution.
Thanks
In addition, I have changed code in the function to create a string seperated by "$" to use a " " instead, however the function is still creating strings using "$", so the old code.
How are you executing your function?
btw, you should probably only parse once π
You are right, I have changed that now!
Also noticed I have sent the wrong function, that one is working fine, This is the one I am having issues with
Then this is how it is excecuted
If I run the function shortly after each other but with different listid, the function will execute with the first listid, and therefore cause an issue as the document already exists, despite the second listid being sent as the value
you can see here the listid sent is the one on ln 267, but the function returns the wrong listid
Btw, I highly advise against using then. It's much clearer to just using async/try/await/catch
Can you try to use req.payload instead of process.env?
Ah perfect, that seems to be working now. Thanks for the help!
[SOLVED] Server Functions Caching variables.
Recommended threads
- Appwrite-injected variables are not avai...
I am using rust-1.83 as a runtime and try to access APPWRITE_FUNCTION_API_ENDPOINT or APPWRITE_FUNCTION_API_KEY during runtime. Both are not set during my execu...
- Functions in cloud console not works
please advise as all of my runing functions on Appwrite console was working before , but now it give this error [Invalid `headers` param: Value must be a valid...
- [SOLVED] Production down - createExecuti...
Hey, Since 1.9.6 rollout in fra (~17:00 UTC, 14 Aug), POST /v1/functions/{functionId}/executions returns a 400 whenever the body includes an empty headers ob...