---
schema_version: "1"
id: 54502266ff23b62fb50b5f64dafae1ab10093ca1a49a81a4efcd0845c1d38ed9
title: Recent Seeds Information and Seeding Job Reports (Salesforce)
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/seeding_o_job_reports.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.seeding_o_job_reports.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 32418c3e6e1126648a990115cc1221d587aa91663653876ba4bf23404c5fad56
description: Seeding application processing generates information about each executed, seeding job Recent Seeds Information, Salesforce Automations Report, Seeding Report. These reports help you in understanding the seeding job's status and outcome.
products:
  - Security
  - Salesforce Platform
release: "264"
---
# Recent Seeds Information and Seeding Job Reports (Salesforce)

Seeding application processing generates information about each executed, seeding job Recent Seeds Information, Salesforce Automations Report, Seeding Report. These reports help you in understanding the seeding job's status and outcome.

## Recent Seeds Information

The Recent Seeds tab (located in the My Templates page) displays a summary about each of the last fifteen seeding jobs that were executed using the seeding template that currently displays in the Template Builder tab.

The table provides the following information per seeding job entry:

- Seed:
    - 1st line: ID of the seeding job. Also, when the clock icon appears to the left of the ID, it indicates that the seeding job was a scheduled seeding job (in contrast to a manually initiated seeding job)
    - 2nd line: Creation <date> <time> of the seeding job
- Source:
    - 1st line: Name of the service used as the seeding source. When a seeding job generated synthetic data as part of the seeding job, the line entry displays Generated synthetic data .
    - 2nd line: ID of the service used as the seeding source. When a seeding job generated synthetic data as part of the seeding job, the line entry is empty
- Destination:
    - If a backup of service data was used, then:
        - 1st line: <date> <time> of the backup
        - 2nd line: ID of the backup
    - If the Live service data was used for the seeding job, then two dash characters (--) display to indicate that column info is not applicable
- Destination: Name of the service used as the destination, whose objects' records had their data modified by the seeding job
- Status (status of the seeding job):
    - Progress bar - a progress bar displays while the seeding job is currently processing. The progress bar annotates both the percent of processing completed and the current processing step.
    - Completed Successfully - all object/table records were successfully seeded.
    - Aborted - seeding processing aborted.
    - Completed with Errors - the seeding job completed, however, processing failed to insert some portion of object/table records (and/or delete some portion of object records, when using the Clean and insert seeding method).
    - Failed - the seeding job failed due to error(s).
- Duration: The amount of time taken by the seeding job
- Seeding job summary, as reported by the following columns:
    - Method - the type of seeding method used
    - Success - the number of object/table records successfully seeded into the destination. Displayed in parentheses, the number of object/table records successfully deleted, when using the Clean and insert seeding method
    - Error - the number of object/table records that failed to be seeded into the destination. Displayed in parentheses, the number of object/table records that failed to be deleted, when using the Clean and insert seeding method
- Seeding Report: Provides access to the seeding job's Seeding Report. Click to view detailed information about the seeding job, including any failures.
- Salesforce Automations Report: Provides access to the seeding job's Salesforce Automations Report. If you selected Salesforce automations to disable during the seeding job, click the Lock icon to view the Salesforce automations that were disabled and then automatically re-enabled upon seeding job completion.

## Salesforce Automations Report

The Automations Report informs you about the Salesforce automations that the application disabled at the start of the seeding job and then automatically re-enabled upon seed completion.

The report includes error and warning messages about the application's disable/re-enable of the requested automations.

Search for an automation by name and/or warning/error message text.

Automations are grouped by their automation type, for example, ValidationRule and ApexTrigger. The groups are collapsed by default. Click a group's arrow to expand its list and view its content - automations with relevant messages.

View the automations that were successfully enabled or disabled.

Each automation group header displays the total number of successes, warnings, and errors.

- ![Success](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-own_from_salesforce-264-0-0-production-enus/8ac98673-ede2-4046-a41e-2d5c846f24ff/own_from_salesforce/images/seeding_o_i_success.png)Identifies that the application successfully disabled the automation at the start of the seeding job and, then, successfully re-enabled the automation upon seed completion.
- ![Warning](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-own_from_salesforce-264-0-0-production-enus/8ac98673-ede2-4046-a41e-2d5c846f24ff/own_from_salesforce/images/seeding_o_i_warning.png)Identifies that the application could not disable the automation at the start of the seeding job.
- ![Failed](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-own_from_salesforce-264-0-0-production-enus/8ac98673-ede2-4046-a41e-2d5c846f24ff/own_from_salesforce/images/seeding_o_i_error.png)Identifies that the application failed to re-enable the automation upon seed completion. The system automatically sends an email notification.
- ![Not disabled](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-own_from_salesforce-264-0-0-production-enus/8ac98673-ede2-4046-a41e-2d5c846f24ff/own_from_salesforce/images/seeding_o_i_not_disabled.png)Identifies that the automation was not selected to be disabled.

At seed completion, in the event that the application fails to re-enable all of the requested automations that it disabled at the start of the seeding job, the job's generated Automations Report presents an error message that informs you of this outcome and includes the link retry enabling:

“Not all automations that were disabled during the seeding job were re-enabled. To try again, click retry enabling.”

Clicking retry enabling causes the application to re-attempt enabling all the disabled automations that it unsuccessfully re-enabled at the conclusion of the seed.

In a seeding template's Recent Seeds tab, only a Destination's most recent seeding job and only for 24 hours from the time that the job completed, does the job's Automations Report present the above error message. After 24 hours from job completion, the job's Automations Report presents the error message Some automations were not automatically re-enabled. Please manually re-enable them.

In the Recent Seeds tab, display a seeding job entry's Automations Report by clicking the Lock icon in the entry's Salesforce Automations Report column.

## Seeding Report

The Seeding report provides information about an executed seeding job. The reported information allows you to troubleshoot issues that prevented records from being inserted into or prevented records from being deleted from (when the Clean and insert seeding method was used) the Destination service. Access a seeding template's seeding reports in its Recent Seeds tab (Seeding > Templates tab > select <template> > My templates page > Recent Seeds tab).

With Classic Salesforce: A recurring activity is comprised of a parent record and a series of recurring child records. When seeding a recurring Salesforce activity, for example, the Event object or the Task object, the series of recurring child records that Salesforce automatically creates/updates/deletes in the destination are not counted in the Seeding Report.

The Summary tab provides an information overview about the seeding job, including the type of seeding method used and a summary of any failed records and the reason they failed.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-own_from_salesforce-264-0-0-production-enus/8ac98673-ede2-4046-a41e-2d5c846f24ff/images/icon_note.png)

Note When a seeding job generated synthetic data as part of the seeding job, the Method column entry displays N/A.

The tab also provides the duration of the seeding job along with a breakdown of the time taken for each of the job's phases. Hover your mouse over the duration timeline to highlight each phase. You can download a full log to help troubleshoot.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-own_from_salesforce-264-0-0-production-enus/8ac98673-ede2-4046-a41e-2d5c846f24ff/images/icon_note.png)

Note The full logs that help to troubleshoot can be very lengthy.

In the Insert & Update Errors tab, the errors table provides information about failed records, grouped by Error type and grouped by Object type. You can drill down and view the error message for each record to identify and fix the cause of the issue.

Click Guide to Common Errors for further information on the errors.

Click the download icon next to the Error and Object toggles, to download a log file containing seeding job results.

The log file can contain these seeding result entries:

- Seeding Result: Error - The Seeding application failed to insert a new record or failed to update an existing record
- Seeding Result: Duplicate - This result is not an error. The Seeding application identified that the record already exists in the destination and, therefore, when the seeding job uses the Incremental seeding method, the record is not re-inserted
- Seeding Result: Skipped - The Seeding application skipped inserting the record. Because the Seeding application could not also insert the record's parent record, therefore, the application did not try to insert the record.
- Seeding Result: Success - The Seeding application successfully inserted a new record or successfully updated an existing record

You can change the grouping of the errors table to group first by Object type and later by Error type, to see the distribution of failures across objects to help identify issues. For example, when one parent object fails to seed, leading to many child object failures.

The Skipped Objects tab is only provided in a Seeding Report if the application has identified missing objects in the following seeding job scenario:

- The executed seeding job used (1) a Levels template and (2) a backup of a service as the seeding source

This tab lists every object missing from the job’s seeding source backup, both root and child objects, included by the Levels template.