After latest Appfarm version several of our actions and core logic are failing:
Database connected DS with cardinality: one and subscribe_to_update: true don’t work. Temporary fix seems to be to disable subscribe to update
Runtime DS throws error Error: Read objects failed: Filter is undefined for filtered selection when action node Read objects tries to populate a cardinality: one runtime DS with a valid filter.
Thank you for reporting these - the first issue is recreated internally. We are working on recreating the second issue, could you post a screenshot of your filter so that we can try and recreate?
The second issue uses a simple <object>.<property> == <urlParamValue>. Running the evaluated filter in GraphQL returns the correct object, so it might be the use of the URL Param that is the issue(?)
Is it possible to rollback the current appfarm version while you resolve these issues? We have some time-sensitive changes we need deployed into production but introducing these bugs will make some of our other critical apps break.
That seems to have fixed the read to runtime DS issue but reveals another issue:
We are using a database connected DS with filter <object>._id == <objectInTempDS> to be able to use the Subscribe to Update feature but the DS fails to load the data.
The client filter on the DS evaluates to false in my tests so it’s not relevant.
The Subscribe to Update has been disabled for now to not increase the complexity.
Are you able to give access to the solution to rhys@appfarm.io? Then I can go in and recreate the setup exactly how it is set up in your solution. This will help our investigations further.