Skip to main content

Understanding Refresh Options in Copado Essentials

A quick breakdown of the differences between Incremental and Full refresh options for your Diff Key flags.

J
Written by Jeff McEvoy
Updated over 2 weeks ago

Overview

Copado Essentials offers two powerful refresh options for metadata comparisons: Incremental Refresh and Full Refresh. Understanding how these options work and when to use them can significantly improve your deployment process.

Incremental Refresh

The Incremental Refresh serves as a quick, efficient option for staying up-to-date with new changes. It works by scanning the source org for newly added components and updating the component list without recalculating all the content. This streamlined process uses Salesforce's sync API to efficiently spot what's new. This approach proves particularly useful during active development when frequent component additions require rapid updates without consuming excessive API calls.

Full Refresh

A Full Refresh provides a comprehensive solution for ensuring complete synchronization. The process begins by clearing the entire cache and then meticulously recalculating all component content and comparisons. This thorough approach becomes invaluable when content changes occur in existing components or when difference flags appear incorrect. While it requires more time than an incremental refresh, it provides absolute certainty about the current state of metadata.

When to Use Each Option

Daily development work typically benefits more from Incremental Refresh, especially during active development and new component addition. However, important deployments or project resumption scenarios call for a Full Refresh to ensure precise metadata alignment. The cache management system handles most situations automatically, with cache expiration occurring every 20-30 minutes, triggering a full refresh to maintain accuracy.

Best Practice Recommendation

The optimal approach combines incremental refreshes during development work with strategic full refreshes before crucial deployments or when switching between different development tasks. This strategy creates an ideal balance between efficiency and accuracy in metadata management.

Did this answer your question?