Skip to content

Clarify Activity timeout defaults/normalization & explain the UpdateOptions merge-clear-normalize behavior #5267

Description

@jsundai

Temporal Affiliation

  • I am a Temporal employee

Page URL

https://docs.temporal.io/activity-operations

Content Issue

When schedule_to_close_timeout is set and either schedule_to_start_timeout or start_to_close_timeout is unset, the unset fields default to schedule_to_close_timeout .
The same normalization happens during start activity, and applies to both SAA and WFA.
docs.temporal.io covers the timeout defaults partially, but it doesn’t clearly explain the UpdateOptions merge-clear-normalize behavior. This can be improved in the docs there and also at CLI/SDK where applicable. Determine pages that need to be changed.

Image

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions