Workflow automation · SDK / API

Temporal

Develop durable software workflows with documented SDKs.

Official documentation Download development spec

TEMPORAL / DEVELOPER FIELD GUIDE

Choose an interface. Define a verifiable result.

Company or project context, ten technical entry points and a practical analysis of every reference.

2026-10-08 · Integration not tested

Company / project overview

Original summary of official company or project statements; use the source for the full original page.

Temporal · About
Project	Temporal provides durable execution for applications whose work spans failures and long waits.
Components	The service persists execution history while application workers run workflow and activity code.
Deployment	Teams can evaluate self-hosting or Temporal Cloud; application workers remain part of the system.

Complete official About page ↗

About reference — TA analysis
Audience	Buyers, partners and product owners shortlisting an AI provider.
Our assessment	Use positioning and company history for initial fit. Obtain project-specific deployment, support and commercial terms separately.

Official sources reviewed. No provider API or inference was run; results are illustrative internal contracts.

Top 10 technical entry points

Ten documented technical entry points selected for implementation decisions, not ten independent SDKs or an official ranking.

Choose by the work you need to complete
Interface	Purpose and audience
01 · Workflow executionAPI / SDK / developer guide	Track durable workflow execution and state.Workflow developers
02 · ActivitiesAPI / SDK / developer guide	Perform external work through activities.Integration developers
03 · WorkersAPI / SDK / developer guide	Run application code while polling task queues.Runtime operators
04 · Retry policiesAPI / SDK / developer guide	Define retry and backoff behavior.Reliability engineers
05 · SchedulesAPI / SDK / developer guide	Start recurring workflow executions.Operations automation teams
06 · Workflow messagesAPI / SDK / developer guide	Use queries, signals and updates for running workflows.Interactive workflow developers
07 · Error handlingAPI / SDK / developer guide	Map application failures into workflow behavior.Python developers
08 · Workflow versioningAPI / SDK / developer guide	Change workflow code while preserving existing executions.Release engineers
09 · Testing suiteAPI / SDK / developer guide	Exercise workflows and activities in test environments.QA engineers
10 · ObservabilityAPI / SDK / developer guide	Inspect workflow behavior with logs and telemetry.Operations teams

Reference analysis

Capabilities summarize official documentation. Constraints and proposed tests are our engineering assessment.

API / SDK / developer guide

Workflow execution

Workflow execution · TA
Target audience	Workflow developers
Documented capability	Track durable workflow execution and state.
Input → output	Workflow input → persisted execution and eventual result.
Execution environment	Temporal Service or Cloud plus compatible application workers; Python examples
Our decision constraint	Workflow code must preserve deterministic replay behavior.
Our suggested validation	Replay recorded histories before releasing changes.

Official reference · Workflow execution ↗

API / SDK / developer guide

Activities

Activities · TA
Target audience	Integration developers
Documented capability	Perform external work through activities.
Input → output	Activity arguments → result or failure.
Execution environment	Temporal Service or Cloud plus compatible application workers; Python examples
Our decision constraint	Retries can repeat external side effects.
Our suggested validation	Use idempotency keys and verify duplicate attempts.

Official reference · Activities ↗

API / SDK / developer guide

Workers

Workers · TA
Target audience	Runtime operators
Documented capability	Run application code while polling task queues.
Input → output	Queued task → worker execution.
Execution environment	Temporal Service or Cloud plus compatible application workers; Python examples
Our decision constraint	A healthy service cannot execute application tasks without matching workers.
Our suggested validation	Check queue names, registered types and worker availability.

Official reference · Workers ↗

API / SDK / developer guide

Retry policies

Retry policies · TA
Target audience	Reliability engineers
Documented capability	Define retry and backoff behavior.
Input → output	Failure and policy → retry or terminal failure.
Execution environment	Temporal Service or Cloud plus compatible application workers; Python examples
Our decision constraint	Unbounded retry may keep business work incomplete.
Our suggested validation	Test retryable and non-retryable failures with deadlines.

Official reference · Retry policies ↗

API / SDK / developer guide

Schedules

Schedules · TA
Target audience	Operations automation teams
Documented capability	Start recurring workflow executions.
Input → output	Schedule and overlap policy → workflow starts.
Execution environment	Temporal Service or Cloud plus compatible application workers; Python examples
Our decision constraint	Time zones, overlap and catch-up policies affect starts.
Our suggested validation	Test missed windows and overlapping runs.

Official reference · Schedules ↗

API / SDK / developer guide

Workflow messages

Workflow messages · TA
Target audience	Interactive workflow developers
Documented capability	Use queries, signals and updates for running workflows.
Input → output	Message → state change or query result.
Execution environment	Temporal Service or Cloud plus compatible application workers; Python examples
Our decision constraint	Read-only queries differ from state-changing messages.
Our suggested validation	Verify message handling during concurrent workflow work.

Official reference · Workflow messages ↗

API / SDK / developer guide

Error handling

Error handling · TA
Target audience	Python developers
Documented capability	Map application failures into workflow behavior.
Input → output	Exception or timeout → handled failure state.
Execution environment	Temporal Service or Cloud plus compatible application workers; Python examples
Our decision constraint	Catching errors must not falsely mark business work successful.
Our suggested validation	Check propagated causes and final business state.

Official reference · Error handling ↗

API / SDK / developer guide

Workflow versioning

Workflow versioning · TA
Target audience	Release engineers
Documented capability	Change workflow code while preserving existing executions.
Input → output	Versioned code and history → compatible replay.
Execution environment	Temporal Service or Cloud plus compatible application workers; Python examples
Our decision constraint	Old histories can conflict with changed command sequences.
Our suggested validation	Replay representative histories before rollout.

Official reference · Workflow versioning ↗

API / SDK / developer guide

Testing suite

Testing suite · TA
Target audience	QA engineers
Documented capability	Exercise workflows and activities in test environments.
Input → output	Fixtures and controlled time → asserted states.
Execution environment	Temporal Service or Cloud plus compatible application workers; Python examples
Our decision constraint	Mocked activities do not prove external integration works.
Our suggested validation	Separate workflow tests from external contract tests.

Official reference · Testing suite ↗

API / SDK / developer guide

Observability

Observability · TA
Target audience	Operations teams
Documented capability	Inspect workflow behavior with logs and telemetry.
Input → output	Execution activity → diagnostic signals.
Execution environment	Temporal Service or Cloud plus compatible application workers; Python examples
Our decision constraint	Avoid exposing sensitive business payloads in logs.
Our suggested validation	Correlate workflow/run IDs across diagnostics.

Official reference · Observability ↗

Official documentation

Official documentation · Supporting reference analysis
TA	Developers and technical product owners
Our validation advice	Pin the release and follow the target-specific support requirements before implementation.

Official reference · Official documentation ↗

04 / INPUT · EXPECTED OUTPUT · ACCEPTANCE

Expected results before implementation

Proposed order-processing workflow contract; this is not a Temporal SDK response. No workflow, activity or external operation was executed.

Illustrative contract · no API call or model execution · not measured provider output

Workflow completed

Expected behavior — illustrative, not executed
Input	Unique order ID and valid order payload.
Expected result	ok only after required activities complete; return workflow/run IDs.
Acceptance	Confirm business outcome and idempotent external effects.

No work required

Expected behavior — illustrative, not executed
Input	Valid order already processed under the same business key.
Expected result	Explicit already-processed/no-op result.
Acceptance	No duplicate external charge or shipment.

Worker offline

Expected behavior — illustrative, not executed
Input	Workflow accepted while matching worker is unavailable.
Expected result	pending/running; no completed business result.
Acceptance	Resume after worker recovery within configured business deadline.

Activity retries exhausted

Expected behavior — illustrative, not executed
Input	External action repeatedly fails under bounded retry policy.
Expected result	failed with cause and compensation state when designed.
Acceptance	Do not promise exactly-once external effects solely from durable execution.

Map the expected result to your application

Map your actual runtime response into this proposed application contract. All values are invented examples; no credentials or live execution are included.

Expected output JSON — illustrative, not measured · Temporal-expected-results.json

{
  "schema_version": "1.0.0",
  "example": true,
  "provider": "Temporal",
  "status": "ok",
  "input_id": "sample-001",
  "data": {
    "workflow_id": "example-order-001",
    "run_id": "example-run",
    "business_state": "completed",
    "result": {
      "order_id": "example-order-001",
      "processed": true
    }
  },
  "error": null,
  "verification": "illustrative-only;not-provider-response"
}

Download specification, example and acceptance plan

Engineering handoff — our proposed contract and gates
State semantics	Valid empty results differ from errors. Pending work must not appear successful before completion.
Evidence	Record service and SDK versions, request identity, configuration and response mapping. No execution or performance was measured here.
Acceptance proposal	Agree numerical tolerances and workload targets before testing on representative authorized samples.

Development assessment

Recoverable quotation workflow

Development concept · integration not tested

Provider capabilities above are based on official documentation or repositories. The proposed product, inputs, deliverable and acceptance criteria below are our development assessment.

Integration pilot

Validate runtime, schemas or hardware together before estimating a deployable product.

Proposed inputs: A sample event, authorized systems and one defined workflow transition.
Proposed deliverable: A visible job state and audit trail for a single workflow.
Acceptance criterion: A retried event must not create duplicate work; an unavailable upstream must remain visibly pending or failed.
Dependencies: Runtime access, workflow permissions and a reviewed notification or write destination.

Development sequence

Confirm access to Temporal, license and the exact supported version.
Prepare the sample above and implement one documented operation for “Recoverable quotation workflow”.
Normalize the result with source, time and explicit error state; keep the provider response for review.
Run the acceptance criterion before estimating rollout effort or committing a customer deliverable.

How to validate demand

Record product views, documentation clicks, specification downloads and contextual hub clicks. These are event counts, not unique people or completed integrations.

This feasibility assessment uses implementation conditions. No traffic-based rank or delivery-time promise is assigned.

Temporal

Choose an interface. Define a verifiable result.

Company / project overview

Top 10 technical entry points

Reference analysis

Official documentation

Expected results before implementation

Workflow completed

No work required

Worker offline

Activity retries exhausted

Map the expected result to your application

Recoverable quotation workflow

Development sequence

How to validate demand

Related products