'unrecognized' volume state when trying to attach several volumes to an instance

It seems that after attaching several volumes to a single instance in parallel, sometimes an 'unrecognized' volume-status is received when querying volume status after the attach operation.

This although the volumes are created in parallel as well, and always get a good status when querying volume-status after creation (status 'available').

Moreover, it seems that trying to query the volume-status of problematic volumes again, a good 'in-use' status is received (which means the volume was attached successfully).

Also important to mention, is that this behavior is not present when attaching volumes in a serial order / in parallel, but to different instances.