Skip to content

Commit b17ec3c

Browse files
jtaylor-csCopilot
andauthored
Update src/content/artifact-management/retention-rules.mdx
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
1 parent a69cec6 commit b17ec3c

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

src/content/artifact-management/retention-rules.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ As a reference, use the `GET` method to retrieve an existing retention rule or t
5757

5858
## When Do Retention Rules Get Evaluated?
5959
1. **Upload Trigger:** A Retention Rule is evaluated automatically whenever a new package is uploaded and completes synchronization. This is the ideal method for triggering a retention rule to ensure packages are evaluated and actioned as expected.
60-
2. **Resync Trigger:** A Retention Rule can also be triggered by resyncing the most recently uploaded package. When using the mechanism, review this documentation to understand how the cutoff date is calculated and how it affects package deletion.
60+
2. **Resync Trigger:** A Retention Rule can also be triggered by resyncing the most recently uploaded package. When using this mechanism, review this documentation to understand how the cutoff date is calculated and how it affects package deletion.
6161

6262
<Note variant="note" headline="Limit by Days: Cutoff Date Calculation">
6363
The cutoff date is calculated by subtracting the Limit by Days parameter value from the upload date of the newest package.

0 commit comments

Comments
 (0)