Skip to content

Drop reset_attempts and reset_heartbeat from UnpauseActivityExecution - #846

Open
dandavison wants to merge 3 commits into
mainfrom
simplify-activity-unpause-wfa
Open

Drop reset_attempts and reset_heartbeat from UnpauseActivityExecution#846
dandavison wants to merge 3 commits into
mainfrom
simplify-activity-unpause-wfa

Conversation

@dandavison

Copy link
Copy Markdown
Contributor

What changed?

  • Drop reset_attempts and reset_heartbeat from UnpauseActivityExecution

Why?

  • They are confusing: they mix Unpause and Reset functionality in a confusing way
  • We have so far been unable to assign desirable and consistent semantics to them during implementation
  • No known user demand
  • They can be added later

A commit for extending this to WFA is reverted in history; we can do this later.

Breaking changes

  • Yes: a user who was using the reset_attempts and reset_heartbeat options of UnpauseActivityExecution will no longer see their effects.

Unpause resumes an activity; it should not also mutate the attempt
counter or discard the heartbeat checkpoint. Neither selective form has
demonstrated user demand, and an operator who wants either would look
for it on Reset. Ship the simple API first.

The field numbers and names are reserved. The deprecated
UnpauseActivity, the batch operations, and the Reset APIs are untouched.

make proto
Drops reset_attempts and reset_heartbeat from the deprecated
UnpauseActivity and from BatchOperationUnpauseActivities, so unpause
means the same thing on every surface. Numbers and names reserved.

The Reset APIs keep their flags: Reset is the operation that restarts an
activity as if on its first attempt.

make proto
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant