Interface: $Properties
external_data.LocalActivityMarkerData.$Properties
Properties of a LocalActivityMarkerData.
Hierarchy
-
$Properties
Properties
activationIndex
• Optional activationIndex: null | Long
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: null | string
LocalActivityMarkerData activityId
activityType
• Optional activityType: null | string
LocalActivityMarkerData activityType
attempt
• Optional attempt: null | number
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: null | $Properties
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: null | $Properties
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: null | $Properties
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: null | number
LocalActivityMarkerData seq