LotusGuild/cinny
3
0
Fork 0
Code Issues 27 Pull Requests 5 Actions Packages Projects Releases Wiki Activity

Status save failed with "server may be rate limiting" — Synapse allows one presence write per 10 s per user #226

New Issue
Closed
opened 2026-09-19 17:43:31 -04:00 by jared · 0 comments
jared commented 2026-09-19 17:43:31 -04:00
Owner
Copy Link
Copy Source

Reported by the owner: changing the status message showed "Failed to save status — server may be rate limiting. Try again." on the first change in a month.

Root cause (verified against Synapse 1.161 source): PUT /_matrix/client/v3/presence/{user}/status is rate-limited by rc_presence.per_user, whose default is per_second: 0.1, burst_count: 1 — one presence write per 10 seconds per user, shared across all of that user's devices — and the servlet answers 429 M_LIMIT_EXCEEDED (with retry_after_ms). Our presence heartbeat (usePresenceUpdater: online/away on visibility and activity changes, from every open tab and the desktop app) spends that budget, so a manual save that lands within 10 s of any heartbeat was refused, and the form treated the 429 as a dead end.

Fixed in f5e7fb47:

  1. The status save waits out Retry-After (bounded ~25 s) instead of failing; the error text now says what actually happened.
  2. The heartbeat dedupes — it only writes when presence or status actually changes (/sync already keeps us online), so it stops consuming the budget.

Reproduced headless with a routed 10 s limiter: heartbeat ok → save 429 → retried 8 s later → saved.

Optional server-side relief (matrix repo / Synapse homeserver.yaml on the host): the default is very tight for a chat with presence badges; rc_presence: {{ per_user: {{ per_second: 1, burst_count: 5 }} }} would let a status change and a heartbeat coexist without the client having to wait. Not required with the client fix.

Reported by the owner: changing the status message showed *"Failed to save status — server may be rate limiting. Try again."* on the first change in a month. **Root cause (verified against Synapse 1.161 source):** `PUT /_matrix/client/v3/presence/{user}/status` is rate-limited by `rc_presence.per_user`, whose default is `per_second: 0.1, burst_count: 1` — **one presence write per 10 seconds per user, shared across all of that user's devices** — and the servlet answers `429 M_LIMIT_EXCEEDED` (with `retry_after_ms`). Our presence heartbeat (`usePresenceUpdater`: online/away on visibility and activity changes, from every open tab and the desktop app) spends that budget, so a manual save that lands within 10 s of any heartbeat was refused, and the form treated the 429 as a dead end. **Fixed in `f5e7fb47`:** 1. The status save waits out `Retry-After` (bounded ~25 s) instead of failing; the error text now says what actually happened. 2. The heartbeat dedupes — it only writes when presence or status actually changes (`/sync` already keeps us online), so it stops consuming the budget. Reproduced headless with a routed 10 s limiter: heartbeat ok → save 429 → retried 8 s later → saved. **Optional server-side relief** (matrix repo / Synapse `homeserver.yaml` on the host): the default is very tight for a chat with presence badges; `rc_presence: {{ per_user: {{ per_second: 1, burst_count: 5 }} }}` would let a status change and a heartbeat coexist without the client having to wait. Not required with the client fix.
jared added the bugpriority: mediumarea: settings labels 2026-09-19 17:43:31 -04:00
jared closed this issue 2026-09-19 17:43:31 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
a11y
Accessibility: keyboard, screen reader, contrast, motion
 area: appearance
Client area: appearance
 area: auth-session
Client area: auth-session
 area: build-ci
Client area: build-ci
 area: calls
Client area: calls
 area: desktop
Client area: desktop
 area: media
Client area: media
 area: messaging
Client area: messaging
 area: mobile
Client area: mobile
 area: moderation
Client area: moderation
 area: navigation
Client area: navigation
 area: notifications
Client area: notifications
 area: settings
Client area: settings
 area: threads
Client area: threads
 bug
Something is not working
 dependencies
Third-party package versions and advisories
 docs
README / LOTUS_* docs wrong or missing
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 needs-human-review
performance
Re-render storms, leaks, heavy work on hot paths
 planning
priority: critical
Data loss, security hole, or crash on a main path
 priority: high
Broken feature or serious usability problem
 priority: low
Minor issue or polish
 priority: medium
Wrong behaviour in an edge case or notable degradation
 qa
Manual QA: shipped, needs a human in a real environment
 question
More information is needed
 research
security
XSS, unsafe URLs, data leaks, auth/session
 tech-debt
Code health, dead code, fragile patterns
 ux
Usability or visual inconsistency
 wontfix
This won't be fixed
No labels area: settings bug priority: medium
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
cole (Cole Keller) jared (Jared Vititoe) nathan (Nathan Vititoe)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: LotusGuild/cinny#226