Yichao YangandGitHub b57133dc84 Detect and fix invalid task generation clock (#6372) ...

## What changed?
<!-- Describe what has changed in this PR -->
- Detect and fix invalid task generation clock by doing a task refresh
- Also fix task refresh API logic now that refresh task also changes the
task generation field in mutable state.

## Why?
<!-- Tell your future self why have you made these changes -->
- Due a backward compatibility issue in cloud, some workflows after
migration could have the wrong task generation clock value.
- Task refresh should persist mutable state update as well.

## How did you test it?
<!-- How have you verified this change? Tested locally? Added a unit
test? Checked in staging env? -->
- New unit test
- Tested workflow refresh locally for open/closed/non-current workflows

## Potential risks
<!-- Assuming the worst case, what can be broken when deploying this
change to production? -->
- Worst case, admin refresh will stop working. 

## Documentation
<!-- Have you made sure this change doesn't falsify anything currently
stated in `docs/`? If significant
new behavior is added, have you described that in `docs/`? -->

## Is hotfix candidate?
<!-- Is this PR a hotfix candidate or does it require a notification to
be sent to the broader community? (Yes/No) -->
- Yes

2024-08-09 15:30:58 -07:00

..

api.go

Detect and fix invalid task generation clock (#6372)

2024-08-09 15:30:58 -07:00