Logs

Every sync operation writes a row to the connector's audit table. The Logs page is the operator-facing window into that table — paginated, filterable, flushable.

Where it lives

WordPress admin → UnoPim Configuration → Logs.

Available to administrators and shop managers.

At a glance

┌─────────────────────────────────────────────────────────────┐
│  Filter: [ All ▼ ] [ All entities ▼ ] [ All channels ▼ ]   │
│          [ Apply ]    Showing 142 rows of 4,801             │
├──────┬──────────┬─────────┬─────────┬──────┬───────────────┤
│ Time │ Status   │ Op      │ Entity  │ Dir  │ Message       │
├──────┼──────────┼─────────┼─────────┼──────┼───────────────┤
│ ...  │ success  │ pull    │ product │ →WC  │ updated SKU.. │
│ ...  │ error    │ push    │ product │ →UNO │ HTTP 422 ...  │
│ ...  │ info     │ push    │ product │ →UNO │ echo suppress │
│ ...  │ info     │ pull    │ product │ →WC  │ dry-run...    │
└──────┴──────────┴─────────┴─────────┴──────┴───────────────┘

Click any row to expand it. You'll see:

• The full message
• A short excerpt of the data sent or received
• Any HTTP code (if applicable)
• How long the operation took
• The channel, language and site context

Filters

Top of the page. All combine.

The Burst filter is a shortcut bundling several criteria — useful for the "show me what just broke" workflow without setting four filters by hand.

Status meanings

Errors are red. Warnings are yellow.

Operations

Direction

A row in detail

Clicking a row expands it. Example for a successful product pull:

Time:        2026-05-05 14:32:01
Status:      success
Operation:   pull
Entity:      product (WC-PRODUCT-001)
Direction:   pull (UnoPim → WC)
Channel:     web
Language:    en_US
Site:        1
HTTP:        200
Duration:    142 ms
Message:     Pulled 28 attributes; 4 categories applied; 1 image queued.

Example for a push that failed:

Time:        2026-05-05 14:32:14
Status:      error
Operation:   push
Entity:      product (WC-PRODUCT-002)
Direction:   push (WC → UnoPim)
HTTP:        422
Duration:    307 ms
Message:     UnoPim rejected the data: attribute "sale_price" is not in this product's family.

Flush controls

Bottom of the page: Flush logs with a scope dropdown.

Confirm dialog. The flush itself is logged as an info entry in the freshly-cleaned table.

Daily auto-cleanup

The connector trims log rows older than 30 days every day, automatically. Your audit table never grows unbounded under normal use.

Common debugging patterns

"Why didn't my product sync?"

1. Set the filter to entity = product and status = error or info.
2. Find the row matching your SKU.
3. Read the message and the data excerpt.

Common causes:

• Cooldown — the product was pushed within the cooldown window after a recent pull
• Skipped by a custom rule — your developer has added a rule that blocked it
• HTTP 422 — a mapping issue (wrong attribute or family)
• Unmapped category — a category mapping is missing
• Missing family — the product has no family and no fallback set

"Why is push slow?"

1. Filter direction = push, sort by duration descending.
2. Outlier rows reveal the slow operations — usually image uploads or large variants.
3. If push is consistently slow, consider turning off image push for that channel, or check UnoPim server capacity.

"Did the scheduled tick fire?"

1. Filter operation = cron.
2. Look for entries around the expected time.
3. If they're missing, scheduled syncs aren't firing — see Troubleshooting → Cron not firing.

Two log layers

The connector also writes a coarse summary line to WooCommerce's standard log under WooCommerce → Status → Logs.

Troubleshooting

The connector also exposes hooks for developers who need to extend it.

Next: Pull