Hi,

I just experienced an issue where a job update was failing and leaving a
lock in place. Expected. What I didn't expect was that while that lock was
in place, it was not possible to interact with any job (old or new) due to
the lock. All the jobs I tested were in the same role and prod environment.

Is this behavior intentional?

I'm working with the 0.5.0-incubating release.

Reply via email to