Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

[Bug] Nondeterminism replaying local activity markers recorded after a FORCE_CLOSE_COMMAND workflow task failure (1.34.0)

Aberta
  • Algo errado?
#1,976 1 comentário 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
8/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
python
Domínio
distributed-systems

Direção de pesquisa

The failure is a replay nondeterminism error, Missing associated machine for LocalActivity(1719), raised when Replayer reprocesses the downloaded history. Start by reproducing it from the sanitized marker metadata, then check how local activity results are ordered within an activation after a FORCE_CLOSE_COMMAND task failure. Done means a replay of that history succeeds without the error. This needs deep knowledge of the workflow state machine and the Rust core, so it is not a first contribution.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

What are you really trying to do?

A workflow fans out ~900 regular activities with asyncio.gather. A workflow outbound interceptor records progress with a local activity: at most one is in flight, and when it resolves a done callback starts the next one with the changes accumulated in the meantime. (We have replaced it with a regular activity as a workaround.)

Describe the bug

While results streamed in, workflow tasks took 2.5-6 s and the server failed them 12 times with WORKFLOW_TASK_FAILED_CAUSE_FORCE_CLOSE_COMMAND (51-139 activity completions arrived during each task). After one of those, the next workflow task (started 08:52:05.021Z, completed 08:52:08.319Z) recorded, in this order:

  • local activity marker seq 1296 (activation_index 1, original_schedule_time 08:52:04.597Z, complete_time 08:52:00.700Z)
  • 422 x ScheduleActivityTask (seq 1297-1718)
  • local activity marker seq 1719 (activation_index 1, original_schedule_time 08:52:04.637Z, complete_time 08:52:02.229Z)
  • 49 x ScheduleActivityTask
  • local activity markers seq 1769 (activation_index 2) and 1770 (activation_index 3)

The complete_time of 1296 and 1719 is before that task started, so both ran during the force-closed attempt (08:52:00.674Z-08:52:04.941Z) and their results were handed to the next attempt.

Any later full replay of this history fails with:

[TMPRL1100] Nondeterminism error: Missing associated machine for LocalActivity(1719)

Replaying the downloaded history with Replayer, the same workflow code and temporalio 1.34.0 fails the same way, so the SDK cannot replay a history it wrote. On the live worker the workflow task kept failing until we terminated the workflow (114 attempts over 16 hours).

Our reading (may be wrong): in the original activation 1, the 1296 result was delivered after the 422 activity resolutions, so the next local activity got seq 1719. activation_index keeps 1296 in activation 1 but not its position among the other resolutions in that activation, so on replay the next local activity gets a different seq.

Minimal Reproduction

We don't have a minimal reproduction yet. The history contains customer data, so we can't attach it, but we can share sanitized event and marker metadata or run a patched build against it.

Shape: asyncio.gather over many activities, plus an outbound interceptor that chains one local activity at a time from done callbacks, plus enough concurrent completions to trigger FORCE_CLOSE_COMMAND (default history.maximumBufferedEventsBatch = 100).

Environment/Versions
  • temporalio (Python) 1.34.0, which includes "Record order LAs are resolved in WFTs" (temporalio/sdk-rust#1616); Python 3.12; Linux container
  • Temporal server 1.31.1, default dynamic config
  • Related: #1881 (closed), #1578 (open)
Additional context

Workaround: send the recording call as a regular activity instead of a local activity.

Linguagem predominante
Python
Estrelas
1.2k
Forks
269
Merge médio
1d 21h
PRs com merge (30d)
56

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de temporalio/sdk-python

Todas as issues de temporalio/sdk-python

Issues semelhantes

Mais issues de Python

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.