* Add .NET reference files for temporal-developer skill Created 11 .NET reference files covering: dotnet.md (overview/quick start), patterns.md, determinism.md, determinism-protection.md, error-handling.md, testing.md, versioning.md, observability.md, data-handling.md, gotchas.md, and advanced-features.md. Follows Python/TypeScript patterns with .NET-specific content for Task determinism, CancellationToken, dependency injection, etc. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * Fix .NET alignment issues from self-review - dotnet.md: Reduce Determinism Rules section to brief cross-reference (was duplicating determinism.md content) - patterns.md: Add ParentClosePolicy to Child Workflows example - gotchas.md: Add missing "Heartbeat Timeout Too Short" subsection - versioning.md: Add missing Key Concepts, Deployment Strategies, Query Filters, PINNED/AUTO_UPGRADE guidance, CLI examples - advanced-features.md: Add worker-level heading for exception types Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * Fix .NET correctness issues from verification pass - patterns.md: Fix cancellation pattern to use official TemporalException.IsCanceledException(e) with detached CancellationTokenSource - advanced-features.md: Fix DI hosting example to use official AddHostedTemporalWorker(clientTargetHost:, clientNamespace:, taskQueue:) pattern Verified against official SDK README, API docs, and temporal-docs. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * Update supported language references to include .NET - SKILL.md: Add "Temporal .NET" and "Temporal C#" trigger phrases, update overview to mention .NET, add .NET entry in getting started - core/determinism.md: Add .NET entry in SDK Protection Mechanisms Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * Edits to advanced features * edits to determinism protection, and move the .editorconfig section * missed one * edit determinism.md * edit error-handling.md * edit gotchas.md * edit patterns.md * edit versioning.md * edit observability.md * fix metrics * self-review round 1 * minor correctness fixed * Update references/dotnet/patterns.md Co-authored-by: Justin Anderson <44687433+jmaeagle99@users.noreply.github.com> * address comments, clarify reference to earlier code snippet * clarify that operations are forbidden IN WORKFLOWS * cleanup workflow cancellation handling example * add task token retrieval comment * update .net requirements * Fix propagation of workflow cancellation --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Co-authored-by: Justin Anderson <44687433+jmaeagle99@users.noreply.github.com>
5.2 KiB
Python SDK Advanced Features
Schedules
Create recurring workflow executions.
from temporalio.client import (
Schedule,
ScheduleActionStartWorkflow,
ScheduleSpec,
ScheduleIntervalSpec,
)
# Create a schedule
schedule_id = "daily-report"
await client.create_schedule(
schedule_id,
Schedule(
action=ScheduleActionStartWorkflow(
DailyReportWorkflow.run,
id="daily-report",
task_queue="reports",
),
spec=ScheduleSpec(
intervals=[ScheduleIntervalSpec(every=timedelta(days=1))],
),
),
)
# Manage schedules
schedule = client.get_schedule_handle(schedule_id)
await schedule.pause("Maintenance window")
await schedule.unpause()
await schedule.trigger() # Run immediately
await schedule.delete()
Async Activity Completion
For activities that complete asynchronously (e.g., human tasks, external callbacks). If you configure a heartbeat_timeout on this activity, the external completer is responsible for sending heartbeats via the async handle. If you do NOT set a heartbeat_timeout, no heartbeats are required.
Note: If the external system that completes the asynchronous action can reliably be trusted to do the task and Signal back with the result, and it doesn't need to Heartbeat or receive Cancellation, then consider using signals instead.
from temporalio import activity
from temporalio.client import Client
@activity.defn
async def request_approval(request_id: str) -> None:
# Get task token for async completion
task_token = activity.info().task_token
# Store task token for later completion (e.g., in database)
await store_task_token(request_id, task_token)
# Mark this activity as waiting for external completion
activity.raise_complete_async()
# Later, complete the activity from another process
async def complete_approval(request_id: str, approved: bool):
client = await Client.connect("localhost:7233", namespace="default")
# Retrieve the task token from external storage (e.g., database)
task_token = await get_task_token(request_id)
handle = client.get_async_activity_handle(task_token=task_token)
# Optional: if a heartbeat_timeout was set, you can periodically:
# await handle.heartbeat(progress_details)
if approved:
await handle.complete("approved")
else:
# You can also fail or report cancellation via the handle
await handle.fail(ApplicationError("Rejected"))
Sandbox Customization
The Python SDK runs workflows in a sandbox to help you ensure determinism. You can customize sandbox restrictions when needed. See references/python/determinism-protection.md
Gevent Compatibility Warning
The Python SDK is NOT compatible with gevent. Gevent's monkey patching modifies Python's asyncio event loop in ways that break the SDK's deterministic execution model.
If your application uses gevent:
- You cannot run Temporal workers in the same process
- Consider running workers in a separate process without gevent
- Use a message queue or HTTP API to communicate between gevent and Temporal processes
Worker Tuning
Configure worker performance settings.
from concurrent.futures import ThreadPoolExecutor
worker = Worker(
client,
task_queue="my-queue",
workflows=[MyWorkflow],
activities=[my_activity],
# Workflow task concurrency
max_concurrent_workflow_tasks=100,
# Activity task concurrency
max_concurrent_activities=100,
# Executor for sync activities
activity_executor=ThreadPoolExecutor(max_workers=50),
# Graceful shutdown timeout
graceful_shutdown_timeout=timedelta(seconds=30),
)
Workflow Init Decorator
Use @workflow.init to run initialization code when a workflow is first created.
Purpose: Execute some setup code before signal/update happens or run is invoked.
@workflow.defn
class MyWorkflow:
@workflow.init
def __init__(self, initial_value: str) -> None:
# This runs only on first execution, not replay
self._value = initial_value
self._items: list[str] = []
@workflow.run
async def run(self) -> str:
# self._value and self._items are already initialized
return self._value
Workflow Failure Exception Types
Control which exceptions cause workflow task failures vs workflow failures.
- Special case: if you include temporalio.workflow.NondeterminismError (or a superclass), non-determinism errors will fail the workflow instead of leaving it in a retrying state
- Tip for testing: Set to
[Exception]in tests so any unhandled exception fails the workflow immediately rather than retrying the workflow task forever. This surfaces bugs faster.
Per-Workflow Configuration
@workflow.defn(
# These exception types will fail the workflow execution (not just the task)
failure_exception_types=[ValueError, CustomBusinessError]
)
class MyWorkflow:
@workflow.run
async def run(self) -> str:
raise ValueError("This fails the workflow, not just the task")
Worker-Level Configuration
worker = Worker(
client,
task_queue="my-queue",
workflows=[MyWorkflow],
workflow_failure_exception_types=[ValueError, CustomBusinessError],
)