I am getting a 500 Error, with the below message (screenshot) in the request history output.
The context is that this is part of a ~20 filter + fuzzy search and sort page on a Bubble front end, sorting across a database of recipes in a Xano back end. The API connection in Bubble is a 'POST' and a 'Data' type.
The fuzzy search is working like a dream and the search and filter seems to be working fine for all but one of the filters 'Months in Season'. The situation where the error appears is in the case where I clear all filters and only filter by values in this 'Months in Season' filter. As soon as I apply any Month value in this filter, there are zero search responses on Bubble and I get this 500 Internal Server error.
Oddly, when this 'Months in Season' filter (which is an array in the bubble API connector, and enters Xano as a list enum input) is applied in tandem with and after first applying one of the other filters, or entering a value to the fuzzy search, it seems to work fine. So I can pass the same array of values for 'month' and it will work depending on whether other filters are also taking a value. I also think this error was not present a couple of days ago.
I am not sure if the issue is in Bubble or Xano. I have tried deleting and rebuilding almost every step touched by the 'months' input in Xano, deleted and rewrote the array in the API connector json, rewrote everything in the multidropdown in Bubble that selects the values. There is a 'cuisine geography' filter that follows exactly the same logic and which works, and I have checked step by step (I think) for any discrepencies between how the 2 filters are set-up and can't find anything. I've tried clearing my browser cache and am about to try previewing in another browser just in case.
Setting up the same values in the Xano 'Run & Debug' as I am entering in the Bubble browser doesn't seem to lead to an error. (Next step is to try and re-initialise the API call with the same values that are throwing the error when I change the filter in the browser)
Normally in situations like this its something simple at the root and I figure it out after following tracks back, but this time I'm flummoxed.
Only thing I can think of specific to this filter that might be connected to this on is that in Bubble, the choices source in the multidropdown is a 'Months' Option set. This was throwing a bug a few days ago and not displaying one of the month values, so I deleted and replaced just that one month. That said - I can't see the logic for how this would play through to an array/scalar error in Xano.
Grateful for any support/ideas!
