I was running into issues trying to implement a different feature (in another bot that checks for existing users and updates their info as needed etc.) and I kept getting tripped up testing any user records that weren't the top row of the table. 🤨 So, I tested it using @bumpy-butcher-41910 's (Check if user input already exists) tutorial bot just to isolate the Find Records issue; AND it's not working as intended here either. No love for stew. 🚫🍲

lemme take a look

so on a fresh bot I was able to recreate the tutorial listed here

even for emails beyond the first record

but I can see that it didn't work in the video you provided

on a test just now, kc@sunshine.co works for me

(yeah we use Chrome, and we recommend using Chrome too)

Thanks for verifying that I am, in fact, sane. 🧘🏻‍♀️

those tend to produce visual bugs

but this is just. odd

you are very sane haha

This issue has gotten even weirder. I created 2 (nearly) identical bots that collect user's email, name and favorite color and store the results in a Table. Now one of the bots has stopped providing ANY correct records, and the other still only finds the top record in the table.

Here's my buggy twin bots that don't behave the same

I use ab@testing.co as the top Table row for testing consistency... in the cloned bot, it still Finds Records (but only the top one) and can update them successfully. The other bot doesn't find anything at all -- even though they are built the same way.

Well, I built yet another bot to test this problem... and it's finally working without bugs. All other bots in this channel are 🥴 REKT at finding records & applying logic... even though they're all built the EXACT SAME WAY.

UPDATE: After much testing and obsessing... I have rebuilt my favorite colors test bot 🌈 yet AGAIN... and now it's working PERFECTLY! I have NO idea why it's suddenly not home to a haunted house worth of bugs, but it is bug free. I make no exaggeration when I say it's the EXACT same bot, built the EXACT same way as the previous ones in this thread... but it works now! Devs, if you're feeling like dipping your toes into some digital madness, try and see if you can find what the h-e-🏒🏒 is going on. Compare the bug & non-bug versions. 🤪

I'm really impressed haha

I know we've been working behind-the-scenes on Tables, my best guess is a newly created bot is working with the latest bug fixes etc

☺️ haha yes... I couldn't let it go. 😅 Thanks to the behind the scenes team working to make Tables even better. 🦾🤖

O M G. This bug is back! In two flavors. 🍨 The test bots' Find Records has stopped working with any new user info. Instead of only recognizing the top row in the table, the filter is ignoring all new rows. (To test add a new row and go through the flow attempting to follow Existing User path.) For new bots (like the BIG one I just remade b/c the old bug was still present in it...) Find Records is back to only recognizing the top row of the table. 🪲

Super interesting nuance to this undead bug. If I enter a row manually in the table, the filter will pick it up using Find Records. BUT, if I enter a new row using the Insert Record card, Find Records returns NADA.

Yup. Same undead bug behavior in the Fav Colors bot too. Seems like some wires are crossed when inserting table records via bot. All works properly when new records are manually entered into the table.

Spooky SZN continues 🙀

Yup. Also verified same undead bot behavior in my BIG bot (not shared in thread).

NOTE: The Insert Record card is correctly adding rows to the Table ✅ BUT rows added in this way are not being picked up by the Find Records filter 🚫

Botpress entomologist reporting for duty. 🤭

For this test bot I added a column to denote the method by which the rows were added to the table. Recap: A manually entered row works great. A bot entered row fails to return the record.

After a month, I'm still seeing this Find Records bug 🐛 where a manually entered table row works great, but a bot entered table row fails to return the record.

Logs for Success: ``Executing AI query { filter: { type: 'AIQuery', template: 'Name is {params[0]}', params: [ 'Jean' ], types: [ 'string' ] } } {"scope":"table","tableName":"NamesAndGenresTable"} AI Query generated successfully { query: { c_1: 'Jean' }, generator: 'function (util, ...params) { return { // "Name is {params[0]}" \'c_1\': params[0] }; }' } {"scope":"table","tableName":"NamesAndGenresTable"} Execute operation findRecords({"filter":{"type":"AIQuery","template":"Name is {params[0]}","params":["Jean"],"types":["string"]}}) { id: 3, createdAt: '2023-12-08T22:52:21.561Z', updatedAt: '2023-12-08T22:52:21.561Z', Name: 'Jean', Music: 'Trance', Manual: true } {"scope":"table","tableName":"NamesAndGenresTable"}`` Logs for Fail: ``Executing AI query { filter: { type: 'AIQuery', template: 'Name is {params[0]}', params: [ 'Sara' ], types: [ 'string' ] } } {"scope":"table","tableName":"NamesAndGenresTable"} AI Query generated successfully { query: { c_1: 'Sara' }, generator: 'function (util, ...params) { return { // "Name is {params[0]}" \'c_1\': params[0] }; }' } {"scope":"table","tableName":"NamesAndGenresTable"} Execute operation findRecords({"filter":{"type":"AIQuery","template":"Name is {params[0]}","params":["Sara"],"types":["string"]}}) {"scope":"table","tableName":"NamesAndGenresTable"}``

@bumpy-butcher-41910 👆🏼

Should I submit a new ticket..?