Product Notice: Bulk API – New retention policy on syncs (Nov 2020)

Version 1

    With the arrival of Eloqua release 20D (Nov 2020), we will begin applying a new retention policy on Bulk API syncs, including sync logs and rejects, that are older than one year. This new retention policy will continue to be applied from 20D on.

     

    What’s changing?

    Currently, Bulk API syncs, including sync logs and rejects, are never removed. Starting in 20D, we will begin applying retention on Bulk API syncs, including sync logs and rejects, that are older than one year. Age of sync is based on the date the sync was created. This new retention policy will continue to be applied from 20D on.

     

    Timeline

    With the arrival of Eloqua release 20D (Nov 2020), we will begin applying retention on Bulk API syncs, including sync logs and rejects, that are older than one year. Check the Eloqua Release Center for specific dates and times.

     

    Next Steps

    If needing any Bulk API syncs, sync logs, or sync rejects information for syncs older than one year, the following endpoints should be used to retrieve and store this information prior to 20D:

     

    Additional Resources

     

    View changes for Eloqua's APIs including, new features, significant recent changes, and platform notices, on the Eloqua Developer Changelog.

     

    If you have questions, post a discussion on Code It!

     

    FAQ

     

    Q: Will definitions used in the syncs also be deleted?

    A: No, definitions are not impacted by this new retention policy.

     

    Q: How do we determine a sync is older than one year?

    A: The age of the sync is determined by the date the sync was created, which is returned as “createdAt” when retrieving a sync.

     

    Q: Why are we implementing retention on Bulk API syncs?

    A: Cleaning up unneeded Bulk API syncs will help with overall stability and performance of the Bulk API.