Throwing error inside CollectionAfterChangeHook will end up creating duplicate items.

I was doing post-update validation inside CollectionAfterChangeHook and throwing errors if something went wrong down the line (in another system which was called using APIs).

It worked well until I realized this one

of throwing errors inside CollectionAfterChangeHook.

⭕ After the error, when user hits SAVE again, a

object is created, not updated as it would be when no errors are throw.