Glitch: Bot will not allow "for each row"

[Patrick_Paul]

I have encountered a glitch in the editor where I cannot create bots that use the "for each row" event type.  Any time I do this, I get an error message as follows:

For each row is selected for the scheduled event, and the tables match.  I have another bot I previously configured in the exact same way with no trouble.  I have done this plenty of times in the past with no issue as well.

[Patrick_Paul]

Ended up deleting entire bot.  Started over, put in the same information and now it works.  Clearly a bug.

[AleksiAlkio]

No, it's not a bug. Your table selections were not correct.. for example the process was using a different table than the task itself..

[Patrick_Paul]

No, that is why I posted it as a bug.  The process and trigger tables were the same, as I stated in the original post.  I've configured countless bots and that's why I posted it as a bug.  The tone of most of the responses I receive on this forum have changed dramatically since I first began using Appsheet 3 or so years ago.  Everyone, especially @Steve were always so helpful when there was an issue.  Recently, on the rare occasion I need assistance or have a problem, the responses range from what amounts to "RTFM" to "You're don't know what you're doing".  Support staff are equally unhelpful.  This is very disappointing.

[AleksiAlkio]

Patrick, please don't take this as a personal critisism, because it's not that. What I have seen within last few years working as a technical specialist after the Bot was officially launched (after preview), I have helped huge amount of customers exactly with this same challenge. Every time when I have investigated the customer's app, the reason has been the setup. That's why I have a strong feeling this goes to the same category. Of course here in community we are all just guessing and giving our strong feelings because we don't have access to your app and possibility to investigate it. 

[Koichi_Tsuji]

• @AleksiAlkio this is bug for sure. 
• the problem is difficult to repro
• however it routinely happens .
• the solution is the delete the bot and create the Same bot from scratch,

furthermore the biggest bug is the Appsheet support desk doesn’t understand what we claim even we register the ticket formally. That is the biggest bug IE google does not have capabilities to digest the voices from the community, you bette to be back to the formal seat in Appsheet team to correct such chaos .