Retain additional cron history by default

There's no reason the clear the history out so fast other than to make it impossible to audit, if / when you have an issue.
magento · Oct 17, 2017 · ba63d94 · ba63d94
1 parent 080a341
commit ba63d94
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 4 deletions.
diff --git a/app/code/Magento/Cron/etc/cron_groups.xml b/app/code/Magento/Cron/etc/cron_groups.xml
@@ -11,8 +11,8 @@
         <schedule_ahead_for>20</schedule_ahead_for>
         <schedule_lifetime>15</schedule_lifetime>
         <history_cleanup_every>10</history_cleanup_every>
-        <history_success_lifetime>60</history_success_lifetime>
-        <history_failure_lifetime>600</history_failure_lifetime>
+        <history_success_lifetime>10080</history_success_lifetime>
+        <history_failure_lifetime>10080</history_failure_lifetime>
         <use_separate_process>0</use_separate_process>
     </group>
 </config>
diff --git a/app/code/Magento/Indexer/etc/cron_groups.xml b/app/code/Magento/Indexer/etc/cron_groups.xml
@@ -11,8 +11,8 @@
         <schedule_ahead_for>4</schedule_ahead_for>
         <schedule_lifetime>2</schedule_lifetime>
         <history_cleanup_every>10</history_cleanup_every>
-        <history_success_lifetime>60</history_success_lifetime>
-        <history_failure_lifetime>600</history_failure_lifetime>
+        <history_success_lifetime>10080</history_success_lifetime>
+        <history_failure_lifetime>10080</history_failure_lifetime>
         <use_separate_process>1</use_separate_process>
     </group>
 </config>