If I had to guess this is likely some kind of automation API bug related to static global state being set in the first run that isn't being cleaned up, and is then causing the second run to fail. You might want to open an issue and see if you can get a small repro together
Not sure it is the same as your case though, but who knows
d
dazzling-salesclerk-51689
05/25/2021, 10:01 AM
@proud-pizza-80589 - no luck on downgrading but thanks.
@bored-oyster-3147 - Yes, agree that it looks like state related issue. opened an issue. thanks.