Troubleshooting Partial Product Uploads
Summary
Learn how to identify and resolve issues when product uploads fail or only partially sync, including how to locate error logs and handle NullPointerExceptions.
Product upload jobs move data from your sources into the Flxpoint Master Catalog or out to your Sales Channels. Occasionally, these jobs may process only a fraction of the expected products or fail silently due to data errors. Understanding how to interpret job logs and identify batching issues is essential for maintaining a synchronized catalog.
Filter Mode and batching
If you are using Filter Mode, products are only added to the Store Catalog if they meet specific criteria. A discrepancy between the total products at the source and the number uploaded often indicates that your filters are working as intended, excluding items that do not match your rules.
NullPointerException errors
A common technical failure is a java.lang.NullPointerException. This occurs when the system attempts to read a data field (like a string or description) that is completely empty or null. In some cases, a single product with a null value can cause a batch to fail or the entire job to halt prematurely.
Check Job Logs: Navigate to the Logs section of your platform. Look for the specific Job ID associated with the failed or partial upload.
Identify Error Strings: Search the log messages for specific error codes or phrases like "Cannot invoke String.length because parameter is null."
Verify Product Count: Compare the number of products in your Store Catalog against the number successfully processed in the job summary to see where the drop-off occurs.
When a job fails due to bad data in a specific product, use these methods to restore the sync:
Data Cleanup: Review the source data for the affected products. Ensure required fields like SKU, Title, and Price are not null or empty.
Manual Retries: After correcting data at the source or adjusting your mapping templates, manually trigger the Get Inventory or Sync job to process the remaining items.
Backend Adjustments: If a job continues to fail silently without listing failed products in the UI, contact support to identify if a specific product is causing a process-level crash that requires a backend patch.
Note: Silent failures (where no products are marked as "failed" in the UI logs) often indicate a code-level exception that prevented the error-reporting logic from finishing.