Vintexvintex.app

The history of everything Vintex did on your accounts — actions you started and automation cycles.

What the log is for

Two questions find their answer here: "what did Vintex do on my account?" and above all "why did my automation do nothing?". The second is the most frequent — and the answer is almost always a legitimate reason, not a failure.

It is the first place to open when an automation looks idle or a bulk action didn't do what you expected.

Vintex activity log, actions and automation cycles interleaved
Your actions and automation cycles, in a single list.

Two sources in one list

  • Your actions — relists, labels, ratings, backups, unfollows… everything you start from the dashboard.
  • Automations — cycle start and end, messages sent, offers, boosts.

Each row carries its Vinted account, timestamp, type and detail.

Reading a cycle that "did nothing"

That is the log's main use. An automation cycle that ends without acting says why, and the reason is rarely a failure:

The line reads Nothing to send, followed by its reason:

Reason shownWhat it means
no favourite in the search periodNothing new — widening the period is the first thing to try
favourites more recent than the delay after favouriteThey will go out on their own later
every favourite already has a conversationThose buyers have already been contacted
buyers already contacted within the resume windowThey got a message too recently
no message configuredNo rule exists
no message applies right nowRule disabled, or outside its day / time slot
insufficient reputationRating below the configured threshold
per-item message cap reachedThe per-item limit is used up
conversation list incomplete, sending postponedThe cycle refuses to send rather than risk a duplicate

Two reasons are not 'nothing to do'

notifications could not be read is a failure, not an absence of work: Vintex couldn't read your favourites, so it tried nothing. Likewise a Quota used up or Subscription unreadable line says the cycle stopped on a blocker. Those three deserve a second look; the reasons in the table above don't.

Filtering

By account, by source (the originating action or automation), by event type and by level — Errors, Warnings. Filtering on Errors shows at a glance what actually failed.

If it doesn't work

SymptomLikely causeFix
Empty logNo Vintex session, or no activityCheck the connection at the top of the sidebar
"Could not load"The Vintex service didn't answerRetry
A cycle doesn't showThe automation never startedCheck that a Vinted tab for the account is open and the automation is active