Strixa AI
TopicsSearchPricing
Sign inStart tracking

Signal Detail

Loading signal detail

Reading this signal card's judgment, risks, and evidence.

Strixa AI
TopicsSearchPricing
Sign inStart tracking
Back to Signal Feed
CodeTracked since May 21, 2026

Deduplicate identical child waiting events using status+output hash

The notifier now suppresses repeated `running→waiting` [EVENT] alerts for the same child when its output has not changed, addressing a case where one dormant child emitted 47 identical wait notifications in 15.5 hours. A new dedup key `(child_id, to_status, last_output_hash)` is applied with a 2-hour TTL, while the legacy 90-second `(from, to)` dedup remains for callers that cannot provide output hash context.

agent-deckstatus-transition notifiertransitionNotifyRecordLastOutputHash

Signal Intelligence

Confidence Level96%
Worth Continued TrackingFinal score 81% with 1 evidence item.
Primary Impact Areas
agent-deckstatus-transition notifiertransitionNotifyRecord

What Happened

  • The notifier now suppresses repeated `running→waiting` [EVENT] alerts for the same child when its output has not changed, addressing a case where one dormant child emitted 47 identical wait notifications in 15.5 hours. A new dedup key `(child_id, to_status, last_output_hash)` is applied with a 2-hour TTL, while the legacy 90-second `(from, to)` dedup remains for callers that cannot provide output hash context.
  • The notifier now suppresses repeated `running→waiting` [EVENT] alerts for the same child when its output has not changed, addressing a case where one dormant child emitted 47 identical wait notifications in 15.5 hours. A new dedup key `(child_id, to_status, last_output_hash)` is applied with a 2-hour TTL, while the legacy 90-second `(from, to)` dedup remains for callers that cannot provide output hash context.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Added output-hash-based deduplication to the status-transition notifier with key `(child_id, to_status, last_output_hash)` to suppress non-progress duplicate wait events, implemented with `Instance.GetLastActivityTime()` as the hash source and persisted in `transitionNotifyRecord.OutputHash` for back-compat-compatible state migration. Added regression tests for same-status/same-hash suppression, output-change re-emit, status-change re-emit, TTL boundary re-emit as liveness ping, and legacy 90-second fallback behavior.

Why Track This

Why It Matters

Operators of agent-deck conductor sessions will see much less notification noise from stalled children, so monitoring and automation avoid repeated useless context rechecks while still receiving real progress updates and periodic liveness confirmation. Technically, deduplication now keys on child + target status + output hash for 2 hours, then re-emits once per TTL to avoid silent stalls, and falls back to the prior 90-second window when callers lack `Instance`-based hash data. Watch next: any path still missing `LastOutputHash` may continue to rely on looser dedup and could reintroduce alert noise under replay or non-instance flows.

Impact

Operators of agent-deck conductor sessions will see much less notification noise from stalled children, so monitoring and automation avoid repeated useless context rechecks while still receiving real progress updates and periodic liveness confirmation. Technically, deduplication now keys on child + target status + output hash for 2 hours, then re-emits once per TTL to avoid silent stalls, and falls back to the prior 90-second window when callers lack `Instance`-based hash data. Watch next: any path still missing `LastOutputHash` may continue to rely on looser dedup and could reintroduce alert noise under replay or non-instance flows.

What To Watch Next

  • Watch whether agent-deck becomes a repeated pattern.
  • Track follow-up changes around AI Agents.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: missing_lastoutputhash_fallback_paths, activity_time_hash_assumption_changes.
Open Topic TimelineOpen Technical EventOpen Original Sourcemissing_lastoutputhash_fallback_paths / activity_time_hash_assumption_changes / ttl_liveness_latency_tradeoff

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

asheshgoplani/agent-deck PR #1144: fix(notifier): de-duplicate identical [EVENT] notifications by (child, status, output-hash) (closes #1142)

A dormant child flickering `running→waiting` every ~20 minutes previously triggered fresh identical notifications each time; the fix now emits once for same child/status/hash and re-emits only after TTL as a liveness ping.