Fixed a bug that would occur when duplicating a Bot that includes a Wait step, where the new Bot's Wait step may not trigger correctly if the wait condition was changed.
Note: This fix prevents the problem going forward but does not retroactively fix existing Bots. If you have an existing Bot with a Wait step that is not triggering correctly and you believe was affected by this, duplicating the Bot again should apply the fix to the new copy (at which point you can delete the broken one).
Rollout changes
None
Preview announcements
Preview feature releases enable you to try out new app features that are not yet fully supported. See Product launch stages.
No new preview features were released today.
In addition, the AppSheet preview program lets app creators try out new app features that are not yet fully supported. For more details and to opt-in, see AppSheet preview program.
You would be better to review your previous posts and chain of the responses in order to give update to the users small voices. What we replied is never reviewed and replied. And then, in turn, all the reported bugs are problems are left untouched and unfixed.
Anyway, we know your next update is sometime in March. We will see your next update in the next month, as your post is now not daily, but basis of “MONTHLY” as I suspected.
See ya in the next month.
I don’t know if this helps, but can any and all Appsheet Devs keep visiting this forum, and being visible? I am so sad about this slow death of AppSheet, it’s still a great product with room to grow. I think that in this vibe coded future it will still be useful, since it enforces good database design to use at any kind of scale, and is limited enough to keep maintenance fairly predictable. Please don’t abandon us Google!
