Hmm interesting - I can definitely dig into this to see if it's actually something that just needs to be fixed. At first glance, though, it definitely looks like the error attribute is being updated asynchronously in a way that makes it challenging to capture.
Would something like the below be a suitable replacement? It seems to provide the requisite conditional logic without locking you in to query chaining.
