Issue Summary

When two backup policies are configured for the same Atlassian Cloud instance covering the same products - but with different storage destinations (e.g., one using legacy Amazon S3 storage and one using Atlassian Internal storage) - backups can intermittently fail or experience significant delays.

Both policies are scheduled to run daily. Although they may be staggered apart in time, on some days there is a small overlap in execution windows. This overlap can cause:

• Backup failures during the overlap window

• Delays in backup completion due to the spike in concurrent requests exceeding processing thresholds

Steps to Reproduce

1. Have two backup policies configured for the same Atlassian Cloud instance covering the same set of products - one using Amazon S3 storage (legacy) and one using Atlassian Internal storage.
2. Both policies are scheduled to run daily (staggered but close in time).
3. On some days, the execution windows overlap slightly.
4. Observe backup failures or delayed completion during the overlap period.

Expected Results

• The system should either prevent assigning the same app/product to multiple policies, or

• Handle concurrent/overlapping policy executions gracefully without failures or excessive delays.

• The system currently allows two policies with different storage types to remain active for the same instance and same apps, leading to the overlap scenario described above.

Actual Results

• When policy A intermittently runs longer it overlaps with policy B start time causing policy B to fail.

Workaround

• Currently there is no known workaround for this behavior. A workaround will be added here when available