--- title: Troubleshooting Scheduled Tasks, Uploads, and Automation description: "Several VendorHearth Pro features depend on WordPress scheduled tasks, file uploads, and automated processes. If reminders, scheduled actions, vendor images, documents, or event maps are not working correctly, use the following steps to identify the problem. ## Understanding WordPress Scheduled…" url: "https://vendorhearth.com/docs/troubleshooting-scheduled-tasks-uploads-and-automation/" updated: "2026-09-23" category: Troubleshooting — System Information, email problems, payment issues, roles/access, common problems --- # Troubleshooting Scheduled Tasks, Uploads, and Automation Several VendorHearth Pro features depend on WordPress scheduled tasks, file uploads, and automated processes. If reminders, scheduled actions, vendor images, documents, or event maps are not working correctly, use the following steps to identify the problem. ## Understanding WordPress Scheduled Tasks VendorHearth uses WordPress cron for supported automated processes. These scheduled tasks allow VendorHearth to perform certain actions without requiring an organizer to manually start them. If WordPress cron is not functioning properly, VendorHearth automation may be delayed or may not run. ## Automated Tasks Are Not Running If multiple automated features stop working, start by checking WordPress cron. Also review: **VendorHearth → System Readiness** Look for warnings involving scheduled tasks or automation. ## Automation Is Running Late WordPress cron normally runs when the website receives traffic. On lower-traffic websites, a scheduled task may not run at the exact minute expected. Hosting configuration can also affect WordPress cron. If delays happen consistently, investigate the site's WordPress cron configuration with your hosting provider. ## Vendor Spotlights Are Not Publishing If a scheduled Vendor Spotlight does not publish when expected, check: - Spotlight status - Scheduled date and time - WordPress timezone - Event date - WordPress cron - System Readiness VendorHearth's automatic Spotlight scheduling excludes events with TBA dates because there is no confirmed event date from which to calculate the publishing schedule. ## Social Media Post Did Not Appear VendorHearth creates Vendor Spotlight content as WordPress posts. Sharing those posts to external social media depends on your site's social-sharing configuration. If you use Jetpack for automatic sharing, verify that: - Jetpack is installed and active - Jetpack is connected - The appropriate social account is connected - WordPress posts can successfully share to that account Test social sharing with a normal WordPress post if necessary. ## Test Spotlight Did Not Publish This may be expected. VendorHearth's **Create Test Spotlight** feature creates a labeled WordPress draft for testing. It does not create a real VendorHearth Spotlight record and does not automatically publish the test post. Open the draft in WordPress to review it. ## Vendor Logo Will Not Upload VendorHearth supports vendor logos in: - JPG - PNG - WebP Vendor logos can be up to **5 MB**. If an upload fails, check: - File type - File size - WordPress upload limits - Server upload limits - File permissions Also try uploading another valid image to determine whether the issue affects one file or all uploads. ## Product Photos Will Not Upload If vendor product photos fail, first determine whether the problem affects: - One image - One vendor - All vendors - All WordPress uploads If WordPress itself cannot upload files, the issue may be outside VendorHearth. ## Event Map Is Missing If an event map was uploaded but is no longer visible: 1. Open the event. 2. Verify that a map is still assigned. 3. Confirm that the image exists in WordPress. 4. Check the WordPress uploads directory. 5. Clear applicable caches. This is especially important after migrating the website. ## Vendor Documents Will Not Upload If a required vendor document cannot be uploaded, check: - The document requirement - File restrictions - WordPress upload configuration - Server upload limits - Available storage - File permissions If every type of WordPress upload fails, investigate the website environment before changing VendorHearth settings. ## Files Disappeared After a Migration VendorHearth may still contain database references to uploaded files even if the actual files were not transferred during a website migration. Confirm that the WordPress uploads directory was included in the migration. Check: - Vendor logos - Product photos - Event maps - Vendor documents If the original site still exists, preserve it until missing files have been recovered. ## Uploaded Image Displays Incorrectly If an image uploads successfully but appears incorrectly: 1. Open the image directly in the WordPress Media Library. 2. Confirm the correct file was uploaded. 3. Clear browser and website caches. 4. Check whether an image-optimization plugin modified the file. 5. Test another image. This can help determine whether the issue originates with VendorHearth or WordPress media handling. ## Scheduled Tasks Stopped After a Site Migration After moving VendorHearth to another server or domain, verify: - WordPress cron - WordPress timezone - VendorHearth System Readiness - Email delivery - Scheduled Spotlights - Automated reminders A migration can change server behavior even when VendorHearth's database settings remain intact. ## Check the WordPress Timezone Incorrect WordPress timezone settings can make scheduled content appear to run at the wrong time. Review: **WordPress → Settings → General** Confirm that the website's timezone represents the timezone your organization uses for event operations and scheduled content. ## Avoid Repeatedly Running Automation Manually If an automated process appears delayed, investigate why before repeatedly triggering the same action. Repeated manual actions can create unnecessary confusion when reviewing communication history, scheduled posts, or other records. ## Check System Readiness Open: **VendorHearth → System Readiness** Review any warnings involving: - Uploads - Scheduled tasks - Automation - Database - Setup status System Readiness can help determine whether the problem is specific to VendorHearth or part of the broader WordPress environment. ## Before Contacting Support Gather: - VendorHearth version - WordPress version - PHP version - Feature affected - Whether WordPress cron is functioning - WordPress timezone - Whether the problem began after a migration - Whether normal WordPress uploads work - File type and size if an upload is failing - Relevant System Readiness warnings - Exact error messages or screenshots Do not include private vendor documents or sensitive credentials unless specifically required through an appropriate private support process. ## Next Step Continue to **Preparing Information for VendorHearth Support** to learn what information to gather when a problem cannot be resolved through the standard troubleshooting steps.