Back off sync frequency, or hard error, if we repeatedly fail to sync

NEW
Unassigned

Status

()

defect
P3
normal
6 years ago
2 years ago

People

(Reporter: rnewman, Unassigned)

Tracking

(Blocks 2 bugs)

Firefox 30
All
Android
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(fennec+)

Details

There's no sense in continuing to try if we constantly bomb out on the same things.

Ideas:

* Repeated failures => longer scheduled intervals
* … => sync only on wifi unless you force or things work again
* If those don't work, enter hard error state.
* If failures are only in a particular engine, track that failure state on a per-engine basis (e.g., don't sync bookmarks until we're on wifi, then hard-error bookmarks).
Assignee: nobody → rnewman
tracking-fennec: ? → 29+
Assignee: rnewman → nobody
tracking-fennec: 29+ → 30+
Priority: -- → P3
This is non-trivial, so pushing back.
tracking-fennec: 30+ → 31+
We should continue to track this for 31+; we'll assign as we get a better picture of outstanding work.
Assignee: nobody → rnewman
I assigned since 31 is closing fast. If this is something we could uplift, then fine.
In the spirit of honesty, this is not something I'll get to before 32, but leaving it in my queue is fine.
Assignee: rnewman → nobody
tracking-fennec: 31+ → +
This makes sense.
Why can't one vote here? Thanks in advance! Sorry for the bug spam!
(In reply to Patrick from comment #5)

> Why can't one vote here? Thanks in advance! Sorry for the bug spam!

We don't have voting enabled for all components.

Voting isn't particularly meaningful here; problems are well understood, but time available to work on them is slim.
Product: Android Background Services → Firefox for Android
You need to log in before you can comment on or make changes to this bug.