Help Fixing things Sync is stuck or slow

Sync is stuck or slow

Slow is the design. Stuck is not, and telling them apart takes about a minute.

If the counter is still moving, it is working. A few hundred items take minutes, because every request waits its turn on purpose.

If the counter has not moved at all for several minutes, check these three things: is the tab still open, are you still signed in, and did Vinted rate-limit you.

What normal looks like

Flogit reads through a queue with a pause between every call. That pacing is the most important code in the product: it is what stops your account producing the burst of traffic that looks like a script.

So a shop of six hundred listings is not a ten-second job, and no setting makes it one. There are settings that make it slower, under Pace in Settings, and on a busy account they are worth using.

The three checks

  1. Is the Vinted tab still open and awake?

    Flogit only runs while a Vinted tab is open. A backgrounded tab that the browser put to sleep stops, and resumes when you come back to it. Nothing is lost; it carries on from where it stopped.

  2. Are you still signed in?

    A session that expired mid-sync stops the reading, because there is nothing it is allowed to read. The page often still looks signed in. Reload it and see.

  3. Did Vinted rate-limit you?

    If you have been doing a lot in a short time, Vinted may be slowing you down at its end. Waiting is the fix. Moving Pace to Careful makes it less likely next time.

Starting it again

Open Inventory and press Refresh. It picks up where it left off rather than starting from nothing, so restarting is cheap and safe to try.

Reloading the Vinted tab is the other safe move. It clears a stale session, a stale security token and a sleeping tab in one go.

If it stops in the same place every time

That is a real bug rather than a slow network. Settings has a Report a problem section: Copy diagnostics puts the details on your clipboard and shows you what it copied. Post that on the board with the item count you got to.

Nothing is lost by stopping

The sync is not a transaction that has to complete. Whatever it read is already stored, and the next run continues from there. Closing the tab mid-sync is not a problem, it is just a pause.

Did this answer it?

If not, say so on the board and the article gets fixed.