Default cleanup schedule is set to fire once an hour at the minute 0, same as daily and weekly snapshots schedules. That leads to getting uncatched exception from Elastic, occurring when trying to delete some snapshots while other are being created.
ConcurrentSnapshotExecutionException[[enonic-xp-snapshot-repo:com.enonic.app.snapshotter--hourly2_2024-09-06t07_34_00.244781700z] another snapshot is currently running cannot delete]
Default cleanup schedule is set to fire once an hour at the minute 0, same as daily and weekly snapshots schedules. That leads to getting uncatched exception from Elastic, occurring when trying to delete some snapshots while other are being created.
ConcurrentSnapshotExecutionException[[enonic-xp-snapshot-repo:com.enonic.app.snapshotter--hourly2_2024-09-06t07_34_00.244781700z] another snapshot is currently running cannot delete]The exception itself should be handled in XP
Need to adjust default values for cleanup to set it to run */30 (or every 30th minute) to reduce chance of overlapping snapshot creation/deletion jobs