# Savepoints Savepoints allow users to capture and restore the state of a policy execution at specific moments during a dry run. * Savepoints have names, each savepoint represents a specific Policy execution path. * Savepoints are used to restore execution context to continue execution from the same point. They can be renamed, or deleted. * Multiple savepoints per policy are supported, up to 5 in total per policy. * The active savepoint is protected from accidental deletion. * Bulk operations (delete all, apply multiple) are available. All major data requests in the UI — including navigation, groups, blocks, and virtual users — can be executed in the context of a specific savepoint by using the savepointIds parameter. This ensures the dry-run session reproduces the exact saved state. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://guardian.hedera.com/guardian-dev/guardian/standard-registry/policies/savepoints.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.