new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

Temporal · all subjects

event history & replay

3 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

WorkflowTaskTimedOut event triggers Sticky Execution cache eviction

When the Temporal Service writes WorkflowTaskTimedOut events to Event History and reschedules timed-out Tasks, it forces a Sticky Execution cache eviction on the Worker holding the Execution. The next Workflow Task for it requires a full cold replay.

Check temporal_workflow_task_replay_latency when task execution latency is high

If Workflow Task execution latency is high, check `temporal_workflow_task_replay_latency` next. When replay latency is high, the Worker is burning its time re-running Event History instead of getting to the new commands. Look for large histories and a slow Data Converter.

workflow_task_replay_latency high values

workflow_task_replay_latency is high if it exceeds a few milliseconds. Workflow Task replay reconstructs Workflow state by re-executing Workflow code from beginning using recorded Event History. Causes of high replay latency: Large Event Histories (long histories take more time to replay as Worker processes all events), slow Data Converters especially those with encryption or external services, large payloads in Activities or Signals that slow replay especially if Data Converter processes them, complex Workflow logic or computationally intensive operations like scheduling many concurrent child Workflows or Activities, frequent cache evictions (workers often evict Workflow Executions from cache due to memory constraints or restarts leading to more replays), and Worker resource constraints (high CPU utilization or memory pressure). Remediation: monitor temporal_workflow_task_replay_latency metric, analyze Event History size and consider Continue-As-New for long-running Workflows, optimize Data Converters for encryption or complex serialization, review payload sizes, profile Workflow code to identify CPU-intensive parts, and manage Worker cache by tuning cache size and eviction policies.

Give your agent this brain