Data freshness — when does the worker run?

A question that comes up regularly: "Does the worker run continuously? How fresh is my data?"Here's what runs in the background, how often, and how to verify the sync state yourself.

What Sellerwerk runs in the background

Sellerwerk has not one worker but several jobs running at different cadences. The important ones:

• Campaign sync — every 15 minutes. Pulls current spend, sales, clicks, impressions per campaign from Amazon. That's the number you see at the top of the dashboard.
• Search-term reports — once daily (around 02:00 UTC). Amazon doesn't deliver search-term data live but as a daily report. So yesterday's search term report is available the next morning at the earliest.
• Profitability aggregation — every 4 hours. Joins spend with sales data and computes margins. Heavier compute, hence less frequent.
• Strategy bucket classification — once daily. Takes 14-day data and sorts keywords into Defend / Attack / Cannibalize / Discover / Optimize.
• Recommendation engine — once daily. Generates the bid suggestions and bleeding-spend warnings that surface in the dashboard.

What happens on worker restart

When a worker server restarts (e.g., during deployment or hardware maintenance), three safety mechanisms kick in:

1. In-flight jobs are resumed. We use BullMQ with Redis persistence — a job in-flight stays in the queue and is completed after the restart.
2. Missed cron slots are caught up.If the restart takes 20 minutes and a 15-min sync slot falls in that window, the next slot picks up the missing period. You don't lose data.
3. On longer outage: explicit user banner.If the worker is down for more than 60 minutes, a banner shows in the dashboard: "Data sync delayed since HH:MM". You know whether numbers are current or not.

How to verify sync state

Three quick checks:

1. Sync timestamp in the dashboard

At the top of the dashboard you see the last data-update timestamp — e.g., "Data current as of 14:30 UTC". If it's not from today, there's a sync problem.

2. Campaign detail view

Click into a campaign. At the bottom you see "Last sync: 12 min ago". With a 15-min cron this should never be older than 30 minutes. If it is: sync isn't running.

3. Force resync (emergency)

Under Settings → Amazon Accountsthere's a button "Sync now". It triggers a manual sync job — useful when you just changed something in Amazon Seller Central and want to see the change in Sellerwerk right away without waiting 15 minutes.

Force resync is rate-limited to 1× per 5 minutes so a new sync isn't triggered every 30 seconds. If the button is greyed out: wait a few minutes.

If data looks stale

If you notice numbers in the dashboard are 1+ days old:

• Read the banner? We surface active sync issues at the top. If the banner says "Sync delayed since yesterday", it's a known problem we're working on.
• Tried force resync? Sometimes only your account is in a stuck state that resolves with a manual trigger.
• Checked token state? Under Settings → Amazon Accountsthe status should be green. On "Token revoked" or "OAuth expired": re-authorize.
• If nothing helps: email support@sellerwerk.de with your org ID (top right user menu) and the sync timestamp you see.

Hosting + availability

Sellerwerk runs on two worker servers at netcup (Nuremberg). Cron jobs are redundant: if one server fails, the second takes over. Planned maintenance restarts happen overnight between 02:00 and 04:00 UTC and are usually under 5 minutes.

On a user-reported case from 2026-04-27 ("data 3 days old"), this exact worker-outage scenario hit — both workers had a problem at the same time. Such cases are rare and we notify via banner once we detect it.

Related: Sync stuck — recovery steps, Automation basics (rules also wait for valid data), Privacy & security (hosting in Germany). For questions: support@sellerwerk.de.