Scheduling guide
Activity | WorkflowTemporal endpoint properties
Common configuration for on-demand execution and optional durable scheduling.
When to use
Use this page while designing, implementing, operating, or troubleshooting scheduled and durable execution.
Behavior
temporalExecutionTypeselects Activity or Workflow generation.taskQueuebinds starters and workers.- Empty
schedulemeans on-demand only; a non-empty value also provisions a Temporal Schedule.
Execution properties
Durable execution settings.
PropertyTypeDescription
temporalExecutionTypeenumGenerated execution type.
RequiredDefault:ActivityAllowed: Activity, WorkflowtaskQueuestringTemporal task queue.
RequiredDefault:defaultworkflowExecutionTimeoutmillisecondsTotal execution limit; zero means no explicit limit.
Default:0Minimum: 0activityStartToCloseTimeoutmillisecondsOne Activity attempt limit.
Default:30000Minimum: 1Activity only.activityHeartbeatTimeoutmillisecondsHeartbeat limit; zero disables it.
Default:0Minimum: 0Activity only.maximumAttemptsintegerMaximum Activity attempts; currently required by the endpoint contract.
RequiredDefault:1Minimum: 1Schedule properties
Optional durable schedule fields.
PropertyTypeDescription
enabledbooleanEnables endpoint registration.
Default:trueschedulestringOptional five-field expression.
scheduleIdstringStable server-side Schedule ID.
Required when schedule is non-empty.timezoneenumSchedule timezone.
Default:UTCAllowed: UTCoverlapPolicyenumScheduled start overlap.
Default:SkipAllowed: Allow, SkipmissedRunPolicyenumMissed scheduled starts.
Default:FireOnceAllowed: Skip, FireOnceProduct-level example
temporalExecutionType: Activity
taskQueue: billing
maximumAttempts: 3
activityStartToCloseTimeout: 30000
schedule: ""