Seems like a bug. Generally shouldn't happen. The "On error" properties on actions do not capture "Unexpected logic errors", such as the "index out of range" exception, or "object does not contain property X" exception, but that shouldn't be the case here, I guess. So, it likely is a bug.
If it can be an unexpected logic error, you could try putting the action into an On block error block and make the block handle the error. Make it continue and go to the end of the block, and enable the "Capture unexpected logic errors" toggle in the block. This is the only way to capture them.
