Welcome to Zuora Product Documentation

Explore our rich library of product information

View prefetch history

Learn how to view the prefetch history for Enrichment processors, including details on automatic and manual runs and their status.

Mediation records a history of prefetch runs for each Enrichment processor for up to 15 days. By default, the prefetch history shows the last 7 days of automatic and manual runs, including their status, trigger type, completion time, and any error code or message.

For enrichment that uses prefetch of Account or Product data, each run also records a 'Source data available at' timestamp. This value reflects the latest update time of the billing records that were loaded into Mediation for that run, and helps you understand how fresh the enrichment data is.

For Data Query–based enrichment, the history shows the processing time for each run, which is the time when the Data Query–based prefetch job completed (successfully or with an error). The 'Source data available at' value is not populated.

  1. On the meter definition that contains your Enrichment processor, access the Enrichment processor settings.
  2. Click the Prefetch button in the upper-right area.
    The Data Prefetch window displays the status of the prefetch and available actions.
  3. To see the detailed history of recent prefetch runs for that processor, click View History.
  4. In the history view, use the filters at the top to narrow the results.
    • Date Range – Filter runs to Last 1 Day, Last 7 Days, or a Custom date range.

    • Status – Filter by Running, Finished, Failed, or Canceled.

    • Trigger Type – Filter by Manual or Automatic runs.

  5. Review the table for run history.

    For each prefetch execution, the history shows:

    • Source Data Available At – For Prefetch‑based enrichment using Account or Product data, this field displays the most recent timestamp of billing records loaded into Mediation during that run. It represents the latest "updated time" among all records included in the prefetch.

      • Example 1: If the billing records loaded into Mediation have updated times of 09:15, 11:30, and 10:05, the value shown will be 11:30.

      • Example 2: If five records are loaded with updated times of 14:02, 14:15, 13:58, 14:07, and 14:10, the value shown will be 14:15.

      This column is not populated for Data Query–based prefetch.

    • Processing Time – The timestamp when the prefetch job completes, whether successfully or with an error. For Data Query–based prefetch, this reflects the completion time of the Data Query job, not the time when underlying data updates are finalized. It indicates when the query execution finishes successfully.

      • Example 1 (Prefetch job): If a prefetch job starts at 01:00 AM and completes at 01:07 AM, the Processing Time recorded is 01:07 AM.

      • Example 2 (Data Query–based prefetch): If a Data Query is triggered at 12:02 AM and the related data updates complete at 12:03 AM, the system records 12:03 AM as the Processing Time because that is when the query execution completed.

      • Example 3 (With error): If a prefetch job starts at 03:15 PM and fails at 03:18 PM, the Processing Time recorded is 03:18 PM.

    • Status – The job status (Running, Finished, Failed, or Canceled).

    • Trigger Type – Whether the run was triggered Manually from the UI or Automatically by the schedule.

    • Errors – A user‑friendly error code or message for failed runs, or empty (--) for successful runs.

  6. Click the Close button to return to the Data Prefetch window when you are done.