diff --git a/monitoring/update-bucket-capacity-info-cronjob/alerts.test.yaml b/monitoring/update-bucket-capacity-info-cronjob/alerts.test.yaml
index a16386d3..9e302722 100644
--- a/monitoring/update-bucket-capacity-info-cronjob/alerts.test.yaml
+++ b/monitoring/update-bucket-capacity-info-cronjob/alerts.test.yaml
@@ -3,33 +3,6 @@ rule_files:
   - alerts.rendered.yaml
 
 tests:
-  - name: Update Bucket Capacity Info CronJob Test Taking Too Long
-    interval: 1m
-    input_series:
-      - series: 'kube_job_status_start_time{job="kube-state-metrics", job_name="artesca-data-ops-update-bucket-capacity-info-1", namespace="zenko"}'
-        values: '0x9'
-      - series: 'kube_job_status_completion_time{job="kube-state-metrics", job_name="artesca-data-ops-update-bucket-capacity-info-1", namespace="zenko"}'
-        values: '_x4 240x5'
-      - series: 'kube_job_status_start_time{job="kube-state-metrics", job_name="artesca-data-ops-update-bucket-capacity-info-2", namespace="zenko"}'
-        values: '_x4 240x5'
-      - series: 'kube_job_status_completion_time{job="kube-state-metrics", job_name="artesca-data-ops-update-bucket-capacity-info-2", namespace="zenko"}'
-        values: '_x9 '
-    alert_rule_test:
-      - alertname: UpdateBucketCapacityJobTakingTooLong
-        eval_time: 4m
-        exp_alerts: []
-      - alertname: UpdateBucketCapacityJobTakingTooLong
-        eval_time: 9m
-        exp_alerts:
-          - exp_labels:
-              severity: warning
-              job_name: artesca-data-ops-update-bucket-capacity-info-1
-            exp_annotations:
-              description: |
-                Job artesca-data-ops-update-bucket-capacity-info is taking more than 240s to complete.
-                This may cause bucket capacity to be out of date and Veeam SOSAPI avalability as risk.
-              summary: update-bucket-capacity-info cronjob takes too long to finish
-
   - name: Update Bucket Capacity Info CronJob Test No Success in 10m
     interval: 1m
     input_series:
diff --git a/monitoring/update-bucket-capacity-info-cronjob/alerts.yaml b/monitoring/update-bucket-capacity-info-cronjob/alerts.yaml
index 63f79a33..fbe040c9 100644
--- a/monitoring/update-bucket-capacity-info-cronjob/alerts.yaml
+++ b/monitoring/update-bucket-capacity-info-cronjob/alerts.yaml
@@ -16,21 +16,6 @@ x-inputs:
 groups:
   - name: update-bucket-capacity-info-cronjob/alerts.rules
     rules:
-      - alert: UpdateBucketCapacityJobTakingTooLong
-        expr: |
-          time() -
-          (sum by(job_name) (kube_job_status_failed{job_name=~"${update_bucket_capacity_info_cronjob}.*"})
-          > sum by(job_name) (kube_job_status_completion_time{job_name=~"${update_bucket_capacity_info_cronjob}.*"})
-          or sum by(job_name) (kube_job_status_completion_time{job_name=~"${update_bucket_capacity_info_cronjob}.*"}))
-          > ${update_bucket_capacity_info_job_duration_threshold}
-        labels:
-          severity: warning
-        annotations:
-          description: |
-            Job ${update_bucket_capacity_info_cronjob} is taking more than ${update_bucket_capacity_info_job_duration_threshold}s to complete.
-            This may cause bucket capacity to be out of date and Veeam SOSAPI avalability as risk.
-          summary: update-bucket-capacity-info cronjob takes too long to finish
-
       - alert: NoSuccessfulUpdateBucketCapacityJobRunIn10m
         expr: |
           time()