Jobs, statuses and retries

Every crosspost and every delist is a job. This page covers what each state means and how to clear a queue that has failures in it.

Jobs are on the Crosspost screen (open).

The states

A job can be waiting for a reason other than its turn. If a marketplace has reached its daily limit, everything queued for it says so and goes out after midnight — nothing needs re-queueing.

Why queued and not instant

The queue paces itself deliberately. Two reasons, and neither is a performance problem to route around:

• Marketplaces rate-limit. A burst of listing activity looks automated, and the response ranges from throttling to suspending the account.
• Extension jobs are serial by nature. Mercari, Depop and Vinted are driven through real pages in a background tab. One at a time per marketplace is the only way that works reliably.

A large batch taking a while is normal. A batch where nothing has moved at all is not — see troubleshooting.

Retrying

Open the failed job and press Retry.

Retrying never creates a duplicate. A retry resumes the same job, and a job that already produced a live listing is not run again. This is why a job that looks stuck is safe to retry: the worst case is it confirms what already happened.

Retry after fixing the cause, not before. Retrying a job that failed for a missing size will fail again the same way.

What to fix, and where

• Missing or invalid field → fix on the item, then retry. Fixing it on the item means it is right for every future crosspost too.
• Connection expired → reconnect at Connections, then retry.
• Extension not responding → reload the Reskale tab, confirm the extension is enabled, then retry.
• Marketplace rejected the category or content → change it in the marketplace panel, then retry.

Every message and its fix: crosspost error messages.

Clearing a batch with many failures

Do not work them one at a time. Failures in a bulk run cluster — three or four causes usually account for the whole list.

1. Filter to failures.
2. Read the reasons and group them.
3. Fix each cause once, on the items.
4. Retry the group.

Ten items missing a size is one fix repeated, not ten investigations.

Half-succeeded jobs

Occasionally a listing goes live but the confirmation is lost — the marketplace accepted it and then the response never arrived, or the tab closed at the wrong moment.

Reskale verifies against the marketplace rather than assuming failure. Marking a live listing as failed would leave an orphan: a listing that exists, that Reskale does not know about, and that therefore can never be delisted automatically. A slower confirmation is the better trade.

On the Crosspost page, Find listings we missed checks Vinted, Depop and Mercari for recent posts that went live without Reskale recording them — ones you finished with the marketplace's own List button, and ones that showed as failed but went up anyway. It links only the listings it can match with certainty and leaves anything ambiguous alone rather than guess. It needs the Reskale extension and for you to be signed in to those marketplaces in Chrome.

If you find a listing on a marketplace that Reskale is still not showing, use Mark as listed on the item to connect them.

Jobs that never start

If jobs sit at Queued and never run:

• For Mercari, Depop, Vinted — is Chrome open, with the Reskale extension enabled? These jobs are worked through by the extension, so they pause when Chrome is closed and carry on when it opens. The Reskale tab itself does not need to be open.
• Has that marketplace hit its daily limit? The job list says so when it has. Those go out after midnight on their own.
• For eBay and Discogs — check the connection is not expired.

If neither, reload the Reskale tab. If jobs still do not move, that is worth reporting — include the job IDs. See contacting support.

Reading job history

Each job keeps what happened: which marketplace, which item, when, and the result. Failed jobs keep the marketplace's own error alongside the translated message.

That detail is the single most useful thing to include in a support request. Screenshot it or copy the text.