Background sync interval never adapts to user activity
Open
Nobody has claimed this yet.
1. to develop
bug
performance 🚀
- Dominant language
- JavaScript
- Stars
- 1k
- Forks
- 348
- Avg merge
- 12h 28m
- Merged PRs (30d)
- 91
Description
Steps to reproduce
- Add an account
- Don't use it for more than three days
- Check the cron job schedule
Expected behavior
Account sync job runs every 6h
Actual behavior
Account sync job runs every hour
Mail app version
5.11/5.12
Nextcloud version
No response
Mailserver or service
No response
Operating system
No response
PHP engine version
None
Nextcloud memory caching
No response
Web server
None
Database
None
Additional info
Feature was introduced with https://github.com/nextcloud/mail/pull/11149 but never worked. Checked app and server code for it. Setting setInterval in run has no effect. Only the value set in the constructor does.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the background-sync entry point and compare the interval assigned in the constructor with the value set in run; the issue identifies setInterval and run as the relevant paths. Reproduce with an unused account and verify that the scheduled sync changes from hourly to every 6h.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100