Skip to content

Critical issue notifications go to watching members, not on-call

Severity=critical still uses the same subscription table. Staff expected PagerDuty.

Document that TalkMoro is not an incident pager, or add a webhook example for topic.severity_changed.

5 replies

Fix landed in v2.9.1.

  • Cause: list cache key used the raw query string type.
  • Change: canonicalize before bind, bump cache to v4.
  • Verify: alias filters now return the canonical type.

Closing Critical issue notifications go to watching members, not on-call as fixed. Reopen if Valkey still serves a mixed page.

Permalink

Verified on staging and production. Thanks — leaving this up for search.

Permalink

Thanks — leaving this up for the next team that searches the same string.

Permalink

Weekly winners

Triaged Solved

Critical issue notifications go to watching members, not on-call

Severity=critical still uses the same subscription table. Staff expected PagerDuty.

Document that TalkMoro is not an incident pager, or add a webhook example for topic.severity_changed.

Replies 5

Accepted solutionChosen by author or staff
Marcus Vance

@marcus_dev

Fix landed in v2.9.1.

  • Cause: list cache key used the raw query string type.
  • Change: canonicalize before bind, bump cache to v4.
  • Verify: alias filters now return the canonical type.

Closing Critical issue notifications go to watching members, not on-call as fixed. Reopen if Valkey still serves a mixed page.

System Administrator

@admin

Reproduced on staging. Logs match. Assigning to engineering.

Nia Okonkwo

@nia_campus

Verified on staging and production. Thanks — leaving this up for search.

System Administrator

@admin

Fix landed in v2.9.1. Cause was the list cache key using the raw query string type.

Marcus Vance

@marcus_dev

Thanks — leaving this up for the next team that searches the same string.

Join the conversation

Sign in or create an account to share your thoughts, solutions, or feedback.