The Operations journal: did your reposts actually run?

Open the Publish page of your dashboard, then click the "Journal" button at the top. A drawer opens with two views: Listings (your drafts, schedules and publications created in Bleam) and Operations — the latter is the one we're covering here.

The journal is per Vinted account: it shows the tasks of the account displayed at the top of the Publish page. If you have several connected accounts, switch accounts with the "Publish on:" picker before opening the Journal.

Four filters sort the list: All, Upcoming, Done, Failures (which includes cancelled tasks). While a task is running, the list updates on its own.

Each row is a task, with its type, item count, date and status:

- Repost — started or scheduled from the Wardrobe, or by auto-restock;
- Publication — scheduled publications, transfers to another account;
- Price change;
- Deletion — and the post-transfer cleanup (deleting the original listing after a transfer);
- Backup.

Possible statuses: Scheduled, Running…, Done, Done with errors, Failed, Interrupted, Cancelled, Suspended — plus two waiting states that explain why nothing is leaving: "Deferred — update required" (your extension needs an update; the task will leave on its own afterwards) and "Waiting for the extension" (no browser with the connected extension is running right now).

Click a row to expand it. You'll find the numbers ("18/20 items processed", "2 failed") and one thumbnail per item, with its outcome:

- Processed successfully (green check);
- Left as a Vinted draft (the "Leave as draft" option was on);
- Skipped (item sold or already deleted, for instance);
- Failed (red dot) — hover the thumbnail to read the reason; on mobile, reasons are listed in plain text under the grid;
- Not attempted (the batch stopped before reaching this item).

Each thumbnail links to the listing on Vinted — after a successful repost, to the new listing. On tasks executed by an old extension version, the per-item detail can be missing: the journal then says so explicitly rather than inventing green checks.

When a batch stops early, the journal states the cause along with the number of items never attempted:

- "batch stopped after 5 failures in a row" — a lasting problem (session, restriction) rather than bad luck;
- "Vinted had a transient problem" — if the "retry later" option was on, unprocessed items leave again automatically;
- "Vinted anti-robot check triggered" — a captcha blocked the session (see Unblock a Vinted captcha);
- "listing temporarily restricted by Vinted" or "Vinted account blocked or suspended";
- "Bleam session expired during the batch", "unsupported browser", or a stop at your request.

"Interrupted" means the extension didn't confirm the end of the run (server watchdog): some items may have been processed anyway — the per-item detail is the source of truth.

If you have the mobile app, the "Scheduled tasks" push notification sends you each batch's outcome without opening the dashboard.

Cancelling doesn't happen in the journal, but from the Wardrobe: every item covered by a scheduled task carries a pill (type + execution date) with a cancel cross. Careful: cancelling removes the task for all the items in the batch, not just the one on the card. A task that is already running can no longer be cancelled.

To reschedule, go through the Wardrobe selection again (Repost → Schedule…).