Skip to main content

Interface: $Properties

Properties of a LocalActivityMarkerData.

Extended by​

Properties​

activationIndex?​

optional activationIndex?: Long | null

Position, within the workflow task, of the activation this resolution was delivered in. Replay must deliver resolutions in the same activations because workflow code can branch on which handles are ready. Absent in markers written by Core versions that predate this field.

activityId?​

optional activityId?: string | null

LocalActivityMarkerData activityId

activityType?​

optional activityType?: string | null

LocalActivityMarkerData activityType

attempt?​

optional attempt?: number | null

The number of attempts at execution before we recorded this result. Typically starts at 1, but it is possible to start at a higher number when backing off using a timer.

backoff?​

optional backoff?: $Properties | null

If set, this local activity conceptually is retrying after the specified backoff. Implementation wise, they are really two different LA machines, but with the same type & input. The retry starts with an attempt number > 1.

completeTime?​

optional completeTime?: $Properties | null

You can think of this as "perceived completion time". It is the time the local activity thought it was when it completed. Which could be different from wall-clock time because of workflow replay. It's the WFT start time + the LA's runtime

originalScheduleTime?​

optional originalScheduleTime?: $Properties | null

The time the LA was originally scheduled (wall clock time). This is used to track schedule-to-close timeouts when timer-based backoffs are used

seq?​

optional seq?: number | null

LocalActivityMarkerData seq