Paul White walks us through some issues:
Initial testing went well, which was a pleasant surprise. Soon enough though, errors started to appear in the tool’s output. That’s not entirely unexpected since ensuring consistent results under high concurrency tends to expose all sorts of niggly edge cases. It’s still an annoyance because debugging edge cases in trigger code can be tricky and laborious.
What was a surprise though was the nature of the error messages.
Read on for the full story. Paul has also created a feedback issue covering a problem with the function.