Scheduling guide
temporalExecutionType: ActivityActivity endpoints
Retryable side-effecting work hosted by generated Temporal workers.
When to use
Use this page while designing, implementing, operating, or troubleshooting scheduled and durable execution.
Behavior
- The runtime starts a deterministic wrapper Workflow that invokes the endpoint Activity.
- Activity timeouts, attempts, heartbeat timeout, and normalized graph priority are applied.
- Activity code may perform network I/O and side effects.
- A Temporal Schedule starts the same wrapper path.
Activity execution flow
SubmitSink or ScheduleBuild stable execution identity.
DurableWrapper WorkflowOwn orchestration and history.
WorkerEndpoint ActivityRun I/O with timeout and retry.
ResultGraph boundaryReturn or collect durable output.
Use cases properties
Activity is the side-effect boundary.
PropertyTypeDescription
External I/OrecommendedHTTP, gRPC, database, filesystem, and third-party calls.
Retriesbuilt inUses maximumAttempts and Activity timeouts.
Long workheartbeatHeartbeats expose progress and cancellation.
Product-level example
temporalExecutionType: Activity
activityStartToCloseTimeout: 30000
activityHeartbeatTimeout: 5000
maximumAttempts: 3