Troubleshooting

Cause: Your Google Sheet is not publicly accessible or the sharing settings have changed.

Fix: Open the Google Sheet, click Share, change the access to "Anyone with the link can view," and save. Then trigger a manual sync from the feed settings.

Cause: The selected sheet tab is empty, the wrong tab was selected, or the column headers are not in row 1.

Fix: Verify that the correct sheet tab is selected in the feed settings. Ensure column headers are in row 1 with no blank rows above them. Check that the sheet contains data rows below the header.

Cause: The sync job may have encountered a timeout or an internal error.

Fix: PBLISH automatically cleans up stuck sync jobs after 2 hours. If the issue persists beyond 2 hours, contact support with the feed ID and the timestamp of the stuck sync.

Cause: The file is not a valid CSV, XLSX, or XLS file, or it exceeds the 10 MB size limit.

Fix: Ensure the file is saved in CSV, XLSX, or XLS format. Check the file size is under 10 MB. If your file is larger, consider splitting it into multiple feeds or switching to Google Sheets.

Cause: A column required by the target platform is not mapped in the feed's column mapping configuration.

Fix: Edit the feed, go to Step 4 (Column Mapping), and ensure all required columns shown in the Required Items section are mapped to source columns. Save the feed and wait for the next generation cycle.

Cause: The image URL column is either not mapped, mapped to the wrong PBLISH field, or the URLs in your data are not valid HTTPS URLs.

Fix: Verify the image URL column is mapped to image_url in the column mapping. Check that all image URLs in your feed start with https:// and are publicly accessible (not behind authentication).

Cause: The catalog was created but not activated, or it was manually deactivated.

Fix: Open the catalog settings and toggle the status to Active. The catalog will be processed on the next scheduled generation cycle.

Cause: The template has not been created yet, or the feed contains no products.

Fix: Open the Catalog Setup Guide and confirm Step 2 (Create Template) is done. Verify the linked feed has products on the Feed Products page.

Cause: The ad platform fetches the catalog URL on its own schedule, which may be less frequent than your PBLISH generation schedule.

Fix: This is expected behavior. Each ad platform (Facebook, TikTok, etc.) has its own crawl frequency for catalog feeds. PBLISH updates the content at the URL on your configured schedule; the platform fetches it on its own schedule. Check the platform's documentation for their catalog refresh frequency.

Cause: Products may be filtered out by a Set, or they may have invalid/missing required field values (e.g., missing image URL or price).

Fix: If the catalog uses a Set, confirm the filter rules. In the generation log, look for "Products Skipped"; skipped rows usually mean validation errors. On Feed Products, confirm required fields are filled for each SKU.