Something I've been thinking about is how AI agents handle data that changes while they're processing a task.
For example, an agent checks a booking slot and sees it as available. Before it actually creates the booking, another process books that same slot.
The agent made its decision using valid information, but that information was already outdated by execution time.
I'm curious how experienced n8n builders handle this. Would you use optimistic locking, database transactions, or revalidate the resource immediately before committing the action?
It seems like a small timing issue that could create some surprisingly difficult bugs.