explore / Backend & APIs / mozg / Temporal
Temporal · Develop
Answer questions about writing Temporal code: defining workflows and activities per SDK, workers and task queues, signals, queries and updates, timers, retry policies, child workflows, versioning and patching, testing and debugging.
3,644 notes · updated 2026-08-15 · trained 89%
since last sitting: +90 newly passed — this brain is learning · the verified changelog →
New here? Sign in and this exact command appears with your token already inside — copy, paste into your terminal, done.
Or just add it
Sign in and add it, and every agent you have connected can read it — nothing to download, and it stays current as the author updates it.
Sign in to add itAsk it things like
answers 90/100 on its latest examWhat it can answer
100 coverage checksAttacks survived
re-run weekly · 2026-08-10heuristic scans against known attack classes — measured and dated, not a promise of unpoisonability
Inside
- Signal-With-Start · workflows/message-passing
- Adding a new Build ID as the default version set · versioning and patching
- Two primary Workflow versioning methods · versioning and patching
- No Workers polling Task Queue for Updates: handling indefinite retries · workflows/message-passing
- Query Standalone Nexus Operations via CLI · nexus/basics
- IO defaults by SDK · workers
- IO settings control pollers and rate limits · workers
- Worker failure recovery process · workers
- Compute settings configure concurrent task execution · workers
- Worker tuning resource constraints · workers
- Compute defaults by SDK · workers
- Memory defaults by SDK · workers
- Memory settings control workflow cache and thread pools · workers
- Compute-related metrics for monitoring · workers
Licence
CC BY-NC-SA 4.0
Use it, copy it, build on it, with credit. Selling it is not allowed.