Skip to content

Commit 813b3f2

Browse files
xuehonggecfan
andauthored
Update articles/logic-apps/logic-apps-limits-and-config.md
Co-authored-by: Esther Fan <[email protected]>
1 parent 22016f1 commit 813b3f2

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/logic-apps/logic-apps-limits-and-config.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -120,7 +120,7 @@ For Standard logic app workflows, you can decrease or increase the 90-day defaul
120120

121121
By default, the app setting named **Workflows.RuntimeConfiguration.RetentionInDays** is set to keep 90 days of data. The host setting named **Runtime.FlowMaintenanceJob.RetentionCooldownInterval** is set to check every 7 days for old data to delete. If you leave these default values, you might see data *up to* 97 days old. For example, suppose Azure Logic Apps checks on Day X and deletes data older than Day X - 90 days, and then waits for 7 days before running again. This behavior results in data that ages up to 97 days before the job runs again. However, if you set the interval to 1 day, but leave the retention days at the default value, the maximum delay to delete old data is 90+1 days.
122122

123-
Retention is always calculated by using the limit in place when the workflow started running, no matter the current limit that's on the workflow.
123+
Run history retention is always calculated by using the run's start time and the retention limit at the time when the run started, not the current retention limit.
124124

125125
#### Portal
126126

0 commit comments

Comments
 (0)