This was caused by a race with another cluster update operation that was
happening when this job ran. I reran the job and it succeeded, so it should
be safe to ignore for now (though we may want to make this more robust in
the future).
On Wed, Jan 31, 2024 at 9:10 PM gacti...@beam.apache.org <
This is your daily summary of Beam's current high priority issues that may need
attention.
See https://beam.apache.org/contribute/issue-priorities for the meaning and
expectations around issue priorities.
Unassigned P1 Issues:
https://github.com/apache/beam/issues/30165 [Bug]: Need to
