Invalid vars: Value must be a valid object

"Status: Image is up to date"

No functions found in the current directory

Looks like my system is possessed.. Let me reboot and try again .. This doesn't make sense

Ran the appwrite reset command hoping to re-setup the project and it wiped my Appwrite.json file 🤦‍♂️🤦‍♂️

Created a test function and the issue seems to be resolved by resetting it

Any way to recreate appwrite.json from the deployed appwrite project ? Else I need to setup all functions again ..

It should only delete the project id 🧐

Yea it fixed the package URI issue when creating new function but the main issue of function actually running is still broken

Please share the function code

As mentioned its the default function with no changes made to the code. Another insight, when I "Execute Now" the function from web console, it completes successfully and logs "areDevelopersAwesome: true" .. But when its triggered by an database document create event it fails with "Invalid vars"

What's docker ps show?

Not sure what you mean, docker ps shows list of containers :/

Share the result please

Anything odd in the logs for the worker functions container or executor container?

Slightly odd the worker functions is up less than the others 🧐

Was looking through those logs and refreshed it in docker desktop so probably that's why .. I think I will try and upgrade to the latest and hopefully that does something.. Is the upgrade path 1.2.1 => 1.3.0, migrate data, 1.3.0 => 1.3.1, migrate data or can I skip any version in between ? Documentation states not to skip

And I see 1.3.3 you patched a migration overriding existing data bug ?

Upgrade to 1.3.4 and run the migrate command

Actually, execute now should be very similar to event based executions...

I still can't figure out where "invalid vars" is coming from

Upgraded and migrated and issue still persists. Going to leave it for now, get some shuteye and pick up again tomorrow. Going to relook at the function that creates the document that triggers this one. What I speculate, given that even a dart runtime container is not created for this function when triggered, its something that fails before this function comes online

I see a dart runtime get 🧐

Figured out a workaround where rather than an document create event trigger I create a function execution from the preceding function and pass the required document id and it works. Event trigger still gives the same error.

Did you try with a different runtime?

No, dint occur to me to try that. Will try later today and confirm