The example below uses a product sync from Specter to WooCommerce, but the same steps apply to any workflow and any integration.

Before you start

• You need the product’s article number (SKU) to search with.
• You need to know which workflow handles the sync you are investigating, and in which direction.

When you want to know whether a specific product has been synced — and when it last happened — you search the jobs of the workflow that handles that sync. From there you can open the job’s logs to see exactly what Kroconnect sent and what the receiving system answered.

How jobs and logs fit together

Every time a workflow runs, it records a job (“jobb”). A job covers one run, for one destination, and lists the items it handled. Within a job, every request Kroconnect made is written as a log entry, with the full request and response body.

So finding out when a product was last synced takes two steps: search the job list to find the run, then open that run’s logs to see what happened in it.

Find the right workflow

Go to Workflows and open the workflow that syncs products from Specter to WooCommerce. Click the workflow title, or the document icon in the row, to reach its jobs.

Each direction is its own workflow. A product sync from Specter to WooCommerce is a different workflow from one going the other way, and stock level sync is separate from product sync. Pick the workflow matching the direction and the type you are investigating — the page header confirms it, showing the workflow’s name, its Type (“Typ”), and whether it is Active (“Aktiv”).

Set the date range

This is the step most often missed. The job list only covers the last 24 hours by default. If the product was last synced a week ago, it will not appear until you change the dates.

Open the date filter and set Start Date far enough back to cover the period you are interested in. The search in the next step then applies across that whole period.

Search for the article number

Type the article number into the search field above the list.

The search matches the references Kroconnect stored for each item in the run, and it is a contains match — so a partial article number works too, and will return every item whose reference contains what you typed.

Reference	For a product
Remote Reference (“Extern referens”)	The product’s article number (SKU).
Remote ID (“Externt ID”)	The product’s id in the source system — for WooCommerce, the numeric product id.

Other workflow types are searchable by the reference that makes sense for them: an order by its order number, a customer by email address, a shipment by its order reference. Stock level sync works the same way as products, by article number.

Reading the job list

Each row is one run that touched your product. The newest run is at the top, so the top row answers “when was it last synced”.

Column	What it tells you
Status	Completed (“Färdig”) — the run finished. Error — it failed. Processing — still running. Pending — queued. Callback — waiting for a response from the other system.
Subject (“Ämne”)	The item the run was about, shown as the workflow type plus the reference that matched your search — for example Product ABC-123.
Started (“Startad”) and Completed (“Färdig”)	When the run began and finished.

Batched runs: if a run handled several products at once, Subject shows one of them plus a +N more (“+N till”) link. Click it to see every reference included in that batch.

Opening the logs

Click the document icon at the end of the row, or the subject, to open View logs (“Visa loggar”) for that run.

Column	What it tells you
Level (“Nivå”)	How serious the entry is — Info for normal progress, Warning and Error for problems.
Title (“Titel”)	What was happening, with the request URL underneath, so you can see which system was called.
Timestamp (“Tidsstämpel”)	When the entry was written.
HTTP Code (“HTTP-kod”)	The response from the system that was called. A green 200 OK is success; a red 4xx or 5xx means the request was rejected.

Click the eye icon on a row to open View details (“Visa detaljer”) — the exact body Kroconnect sent and the exact body it received, formatted for reading. This is where you see the product data that actually crossed over: prices, stock levels, names, and any error message the receiving system returned.

The header also has Remote IDs (“Externa ID:n”) and Remote References (“Externa referenser”) buttons, listing every item that was part of the run.

If you don’t find the product

Work through these in order:

• Widen the date range. By far the most common cause — the default covers only the last 24 hours.
• Check the workflow. Right direction, right type? A stock level change will not appear in a product workflow.
• Try the other reference. If the article number finds nothing, try the product’s id in the source system.
• Check the article number itself, including any prefix or suffix. The match is on contains, so a shorter fragment casts a wider net.
• *Turn off Exclude incoming.* See below.
• *Use Refresh (“Uppdatera”)* if you suspect you are looking at cached data.

Exclude incoming: this filter is on by default. Each run consists of an incoming job, where Kroconnect collects data from the source system, followed by one job per destination that receives it. The default hides the incoming job so you see the deliveries — normally what you want, since that is where you find out whether WooCommerce accepted the product. Turn it off to check whether Kroconnect collected the product from Specter in the first place.

Only failures interest you: set the Status filter to Error to list just the runs that went wrong.

If nothing turns up across a wide date range, the product genuinely has not been picked up by that workflow. The usual reasons: it does not meet the workflow’s criteria in the source system, it has no article number (products without one are skipped, since they cannot be matched in the receiving system), the article number contains å, ä, ö or a special character, or the workflow is paused.