--- sourceDocument: Australia Build or modify applications sourceDocumentLink: https://www.servicenow.com/docs/r/australia/application-development Release : - australia ft:locale : - en-US ft:publication_title : - Australia Build or modify applications ft:clusterId : - cadev bundleId : - cadev workflow : - Development, Data, and Analytics --- # Checkpoints and conversation change log # Checkpoints and conversation change log {#ariaid-title1} Release version: Australia Updated August 25, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Checkpoints and Conversation Change Log The conversation change log in ServiceNow Studio automatically tracks every modification Build Agent makes to your application during your development conversations. It provides an integrated view where you can monitor changes, roll back to previous states, and manage deployments through update sets. This capability enhances control and transparency over your application development process. Show full answer Show less ## Key Features * **Change Tracking:** View all changes made since the last checkpoint, including detailed file lists categorized as in the Studio Navigator. * **Checkpoint Management:** Checkpoints group related changes and are created automatically after task plan approval. You can revert your application to any previous checkpoint to restore earlier states. * **Rollback and Restore:** Easily roll back changes to a prior checkpoint if needed, ensuring safe experimentation and development. * **Update Set Integration:** Each checkpoint packages changes into an update set that can be accessed and managed directly within the change log. This streamlines deployment and migration processes. * **Manual Edit Update Sets:** Changes made manually during development are tracked separately; Build Agent assesses these before creating new checkpoints and removes empty manual update sets. ## Practical Implications for ServiceNow Customers This feature enables developers and administrators to maintain rigorous control over application changes made through Build Agent. By automatically creating checkpoints and associated update sets within the same application scope, you can easily merge and move updates between environments without scope conflicts. The change log's visibility into update sets and the ability to open them directly supports efficient deployment workflows. Additionally, the rollback capabilities provide a safety net during iterative development, reducing risk. Understanding how checkpoints correspond to update sets and the nuances regarding scope (especially with Australia Patch 3 and earlier) helps ensure smooth management and migration of application changes. The conversation change log tracks every change Build Agent makes to your application. It appears automatically in an integrated tab in ServiceNow Studio and lets you view updates, roll back to a previous checkpoint, and deploy changes to an update set. ## Conversation change log {#ba-conversational-change-log__section_pkp_1k3_sjc} Use the conversation change log to do the following actions: * View the changes you have made since a checkpoint * Roll back changes to the previous checkpoint * Approve and deploy changes to an update set {#ba-conversational-change-log__ul_cdj_tph_53c}When viewing the conversation change log, you can also view update sets created by Build Agent from within the chat panel. Each checkpoint includes a button that opens the relevant update set in a new tab. For information on how the change log and checkpoints work with update sets, see [Update sets and Build Agent](https://www.servicenow.com/docs/25K10uRGfz2uc5gvqIreEA "When you work with Build Agent, your changes are automatically tracked in update sets so you can review, revert, and deploy them without leaving ServiceNow Studio."). The change log displays the following: * The Files list displays all the files that Build Agent updated during your conversation. The categories mirror the ones in the ServiceNow Studio Navigator panel. * The menu at the top shows the current checkpoint. You can use the list at the end of the checkpoint name to select a different checkpoint to view. When there are multiple checkpoints, a Summary option appears, which shows changes from each checkpoint all together. * The overview section shows the plan and actions Build Agent took based on the conversation. * The action in the corner menu to pen the chat, Restore your app to a previous checkpoint, or open the app details page. Changes from each checkpoint in the conversation are packaged together into an update set. You can find each update set on the Deployment tab on the ServiceNow Studio home page. For more information on deployment, see [Deploying what you built with Build Agent](https://www.servicenow.com/docs/UfO9v7wOOeW1T_UazSmw1A "Learn about deployment methods and workflows for moving applications created with Build Agent from development to production environments. Choose the right deployment approach based on your application complexity and organizational requirements."). ## Checkpoints {#ba-conversational-change-log__section_pxq_dk3_sjc} Checkpoints are groups of changes that you made to an application that you can revert to at any time during your conversation with Build Agent. Checkpoints are created automatically after you approve each task plan. Note: With Australia Patch 3 and earlier, checkpoint 0 creates an update set in global scope, and subsequent checkpoints created update sets in your application scope. However, update sets that exist across different scopes and can't be merged. * Checkpoint 0 creates an update set in global scope, and subsequent checkpoints created update sets in your application scope. However, update sets that exist across different scopes and can't be merged. * Checkpoint 0 doesn't create an update set. Instead, it serves as a placeholder in the UI that you can use to restore your application to its initial state. * Checkpoint 1 is the base update set for your application. The checkpoint 1 update set is the parent, or chain root, for all subsequent update sets created during the conversation. Because all update sets exist in the same application scope, you can merge them together when you're ready to move your changes to another environment. For information on update sets, see [Update sets and Build Agent](https://www.servicenow.com/docs/25K10uRGfz2uc5gvqIreEA "When you work with Build Agent, your changes are automatically tracked in update sets so you can review, revert, and deploy them without leaving ServiceNow Studio."). {#ba-conversational-change-log__ul_pkh_gk3_sjc} Figure 1. Checkpoints card When Build Agent prepares to create the next checkpoint, it checks whether any changes exist in the manual edit update set. If no changes are present, Build Agent removes the update set. If changes exist, Build Agent completes the update set and renders it with the other update sets from your conversation. You can access manual edit update sets directly from the checkpoints panel in your Build Agent conversation.