Webhook retries deliver a duplicate payload
100% of problems resolved · median first response 9h
A failed webhook is retried without an idempotency key, so downstream systems process the same event twice.
Environment
Web · Chrome 141 · macOS 16
Response timeline
Every state change is public, including the company's reasoning.
Reported
Jun 9, 2026Felix Chen reported this problem.
Other Tallyhawk problems
Session expires without warning mid-edit
The session ends silently while editing, and unsaved work is lost on the next save attempt with no warning beforehand.
Integration disconnects silently after token refresh
When the upstream token rotates the connection drops without notifying anyone, and sync stops until someone notices manually.
Recurring items shift by an hour across DST
Items scheduled before a daylight-saving change fire an hour out afterwards, which breaks anything time-sensitive.