Weekly Maintenance

This document describes the maintenance tasks that should be carried out once per week on a production site running the ADP Car Market Hub plugin. These tasks go deeper than daily checks and are designed to keep the inventory, logs, and configuration in good shape over time.

When to use this document

Read this document if you manage a live site that uses the plugin and you want to maintain a stable, well-monitored installation. Weekly maintenance is typically performed by a site administrator or a dealership IT contact.

Overview

Daily checks confirm that background processes are running. Weekly maintenance reviews the results of those processes in more detail: log volume, import quality, lead pipeline health, analytics trends, and cron reliability. It also provides an opportunity to act on any issues that have been accumulating across the week.

Requirements

• Administrator account with the manage_as24_imports capability.
• Access to WordPress Admin → ADP Car Market Hub.
• Access to the WordPress admin dashboard (Dashboard → At a Glance or the plugin's own dashboard widget, if enabled).

Weekly tasks

1. Review the full import log

1. Open ADP Car Market Hub → Logs.
2. Set the Lines field to a higher value (for example, 500 or 1000) and click Reload to see more history.
3. Scan for patterns: recurring errors, repeated API failures, or listing IDs that consistently fail.
4. If the log file is very large, consider whether verbose logging needs to remain enabled. Verbose logging (configurable in the Logs or Settings area) logs a line for every vehicle and every image action. On large catalogues this can generate significant log volume.
5. If old errors have been resolved, clear the log file using the Clear log file button to start with a clean baseline for the coming week.

2. Audit import counts

1. Open ADP Car Market Hub → Import & Limits and review the Last run status summary (inserted, updated, skipped, errors).
2. Compare the total local vehicle count (shown in the Dashboard KPI row) with what you expect based on the AutoScout24 listing inventory.
3. If the local count is lower than expected, check whether the Full sync option is enabled (under Automation / Import settings). When enabled, vehicles that are no longer present in the AutoScout24 listing are automatically deleted from the local site after each import. If vehicles are being deleted unexpectedly, review whether this setting is appropriate for your workflow.
4. Check whether any vehicles are stuck in draft status when they should be published. The default post status is configured under Settings → Default post status.

3. Triage and process leads

1. Open ADP Car Market Hub → Leads.
2. Review leads that have not yet been processed. Mark them as Contacted, Closed, or Spam as appropriate.
3. If a large number of spam leads are appearing, consider reviewing the contact form configuration. A GDPR consent checkbox is available in the lead form settings.
4. Verify that the lead notification emails are reaching the correct recipient. Check the Lead recipient email setting if emails are going to the wrong address.

4. Check analytics trends (if analytics is enabled)

1. Open ADP Car Market Hub → Analytics.
2. Review the period selector (7, 14, 30, 90, or 180 days) and examine page view trends, top-performing vehicles, and any Business Intelligence events (filter searches, contact form opens, leads sent).
3. Identify listings with unusually low views. These may benefit from content improvements, better images, or pricing adjustments.
4. Confirm that analytics data is being collected. If the tracking pixel is not firing, verify that Analytics is enabled under the Analytics tab settings and that a consent management plugin (if in use) is not blocking the tracking endpoint.

5. Verify cron reliability

1. Open ADP Car Market Hub → System & Help.
2. Review the External cron status indicator if you are using server cron mode. The plugin records the timestamp of the last external ping. If the last ping is older than expected, investigate the server cron job configuration.
3. Confirm that the import schedule in the Import & Limits tab matches operational requirements. Available schedules include: hourly, every 6 hours, twice daily, daily, and a configurable custom interval (minimum 15 minutes).
4. If imports are running but image downloads are falling behind, consider whether the Image queue cron batch size or frequency needs adjustment.

6. Review the image queue

1. Open ADP Car Market Hub → System & Help.
2. Inspect the current image queue size. A healthy site will show a small or empty queue.
3. If the queue has grown over the week, use the Trigger image queue now button in the Import & Limits tab to process it, then investigate whether the image-queue worker is scheduled correctly.
4. The image queue worker processes 30 images per batch by default. On sites with large catalogues, multiple consecutive runs may be needed.

Operational notes

• Log rotation happens automatically when the log file exceeds 10 MB. Archived logs are deleted after 7 days. If you want to retain logs longer, download or copy the archived log files before they are purged.
• The analytics table ({prefix}as24ci_analytics) is cleaned up automatically by a daily WP-Cron job based on the configured Analytics retention period (default 180 days). Verify this retention period under the Analytics tab settings.
• Scheduled import runs acquire a transient lock that is automatically released after the import completes. If a lock persists longer than 40 minutes, it is automatically cleared on the next run attempt.
• The plugin records the timestamp of the last import run in the WordPress options table (as24ci_last_run_time). This value is used to display the last-run indicator in the Dashboard and Import & Limits tabs.

Troubleshooting

Related documents

• Daily Operation
• Logging and Monitoring
• Import Monitoring
• Image Queue Maintenance
• Monthly Maintenance