github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-09 11:42:54 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[Feature]: Change error for 429 Too Many Requests #1743

New Issue
Closed
opened 2026-02-28 19:53:36 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-02-28 19:53:36 -06:00
Owner
Copy Link

Originally created by @louwers on GitHub (Jan 5, 2025).

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

When the server returns status code 429 Too Many Requests, a message is shown that Sync failed encouraging the user to open a GitHub issue with a bug report.

We had problems syncing your changes. Please report this as a bug by opening a Github issue.

When a 429 Too Many Requests status code is returned, it's not an error, a different error message should be shown "Could not sync due to too many requests, please try again later." or something similar.

How can we reproduce the issue?

I don't know why the too many requests issue showed up. But Actual seems to be spamming various endpoints.

Just spoof a 429 response and you'll see the message appear.

Where are you hosting Actual?

Pikapods

What browsers are you seeing the problem on?

Chrome

Operating System

Mac OSX

Originally created by @louwers on GitHub (Jan 5, 2025). ### Verified issue does not already exist? - [X] I have searched and found no existing issue ### What happened? When the server returns status code 429 Too Many Requests, a message is shown that Sync failed encouraging the user to open a GitHub issue with a bug report. > We had problems syncing your changes. Please report this as a bug by [opening a Github issue](https://github.com/actualbudget/actual/issues/new?assignees=&labels=bug&template=bug-report.yml&title=%5BBug%5D%3A+). When a 429 Too Many Requests status code is returned, it's not an error, a different error message should be shown "Could not sync due to too many requests, please try again later." or something similar. ### How can we reproduce the issue? I don't know why the too many requests issue showed up. But Actual seems to be spamming various endpoints. Just spoof a 429 response and you'll see the message appear. ### Where are you hosting Actual? Pikapods ### What browsers are you seeing the problem on? Chrome ### Operating System Mac OSX
GiteaMirror added the featureneeds votes labels 2026-02-28 19:53:36 -06:00
GiteaMirror commented 2026-02-28 19:53:37 -06:00
Author
Owner
Copy Link

@matt-fidd commented on GitHub (Jan 17, 2025):

I can't replicate the 429 organically, do you have any network logs showing what endpoints are being spammed?

@matt-fidd commented on GitHub (Jan 17, 2025): I can't replicate the 429 organically, do you have any network logs showing what endpoints are being spammed?
GiteaMirror commented 2026-02-28 19:53:37 -06:00
Author
Owner
Copy Link

@louwers commented on GitHub (Jan 17, 2025):

I also cannot reproduce it, that's why I suggest changing the error message at least.

@louwers commented on GitHub (Jan 17, 2025): I also cannot reproduce it, that's why I suggest changing the error message at least.
GiteaMirror commented 2026-02-28 19:53:37 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jan 17, 2025):

✨ Thanks for sharing your idea! ✨

This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make a successful contribution).

The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+

Don’t forget to upvote the top comment with 👍!

@github-actions[bot] commented on GitHub (Jan 17, 2025): :sparkles: Thanks for sharing your idea! :sparkles: This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make a successful contribution). The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+ Don’t forget to upvote the top comment with 👍! <!-- feature-auto-close-comment -->
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label feature needs votes
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#1743
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?