KatanaPIM Cron Jobs for Magento 2 Synchronization

The Full Update cron fetches ALL data from the KatanaPIM API but does not sync to Magento directly.

What it does:

1. Fetches all attributes, categories, products, and assets from KatanaPIM API
2. Stores the data in intermediate tables (katanapim_product, katanapim_category, etc.)
3. Calculates hashes to detect changes
4. Sets the needs_update flag on items where PIM data differs from Magento
5. Marks items no longer in PIM as deleted

What it does NOT do:

• Create or update Magento products
• Create or update Magento categories
• Import images into Magento

The Incremental Update cron processes items marked for update and syncs them to Magento.

What it does:

1. Fetches recently changed items from KatanaPIM API (using timestamp filter)
2. Processes all items with needs_update = 1
3. Creates or updates Magento products, categories, and attributes
4. Imports images and videos into Magento
5. Clears the needs_update flag after successful sync

The module uses two separate hash comparisons:

1. During API fetch (Full Sync):

2. When saving to intermediate table:

This means: if data hasn't changed in KatanaPIM since the last Full Sync, the item is skipped entirely and needs_update won't be updated.

After a successful Magento sync:

1. The item is created or updated in Magento
2. mapped_magento_hash is set to match mapped_katana_hash
3. needs_update becomes 0

Items are only synced to Magento when ALL conditions are met:

• needs_update = 1
• skipped = 0
• is_deleted = 0
• has_error = 0

The cron limits primarily affect the Incremental Sync, which processes items from the intermediate tables to Magento.

If 500 products have needs_update = 1, but the limit is 100:

• First cron run: processes products 1-100
• Second cron run: processes products 101-200
• And so on...

With a 5-minute incremental schedule, all 500 products would be synced within ~25 minutes.

Schedules can be configured in Stores → Configuration → Katana PIM → Automation.

Check the flags:

SELECT sku, needs_update, skipped, is_deleted, has_error
FROM katanapim_product
WHERE needs_update = 1
LIMIT 10;

Items need needs_update = 1 AND skipped = 0 AND is_deleted = 0 AND has_error = 0 to be processed.

Verify cron is active:

bin/magento cron:run --group=katanapim

Check cron schedule:

SELECT * FROM cron_schedule
WHERE job_code LIKE 'katanapim%'
ORDER BY scheduled_at DESC
LIMIT 20;

Options:

1. Increase cron limits (see "Adjusting Limits" above)
2. Reduce incremental schedule frequency
3. Run full sync via CLI during off-peak hours instead of cron

If items are incorrectly marked as deleted, it usually means:

• The item was removed from KatanaPIM
• API connection failed during full sync (partial fetch)

Fix: Run a manual full sync via CLI to re-fetch all data:

bin/magento katana:import:full --products