Skip to main content
Video tutorial · 0:57

Bulk renew

Select many certificates at once and submit a single action. The backend fans out individual renewal jobs, tracks per-cert progress, and aggregates the outcome. Idempotency keys prevent double-submission of the same batch; partial failures surface as partial_failure with the failed certs callable out for human attention.

Why bulk vs individual​

  • CA/B Forum shortening. SC-081 (47-day certs) means your renewal cadence goes from every 60–90 days to every 20–30. Bulk actions are how you absorb that volume without clicking a thousand buttons a week.
  • Quarterly audits. "Renew every cert issued before date X" is a common ask — bulk action + filter.
  • One tracked action. A bulk renew is a single job-based fan-out with a per-certificate result breakdown, rather than a series of unrelated clicks. Note it does not project CA rate limits for you — check your CA's quota yourself before submitting a large batch.
  • The same guards as a single renewal. While the project's approval policy gates renewal for an operator, bulk renew is not available to that operator (refused with APPROVAL_REQUIRED); renew each certificate individually to raise an approval request. Admins and owners bypass the gate, and one auto-executed approval record is written for the bulk action (resource type bulk_action, naming how many certificates it carried). The licence certificate limit applies, and bulk actions are limited to 10 per minute per project — one action can carry up to 10 000 certificates, so the request count is what bounds how fast renewals can be driven at the CA.

Prerequisites​

  • Operator role on the project.
  • Each selected cert has a healthy issuer (or you're explicitly using bulk renew to restart a stuck cert).

Submit a bulk action​

  1. Certificates → filter / search to your working set.
  2. Tick the row checkboxes (the header checkbox selects the current page). Imported certificates cannot be selected — they cannot be renewed.
  3. Click Renew Selected. The confirmation dialog shows how many certificates the action applies to.
  4. Confirm. The backend creates a bulk_action record with a SHA-256 idempotency key and enqueues one renewal per certificate.
  5. A progress bar on the Certificates page tracks the action until it finishes; when it ends in partial_failure, a Bulk Action Results dialog lists every failed certificate with its error.

Bulk action states​

StateMeaning
pendingRecord created; renewals not yet enqueued.
in_progressRenewals enqueued; results still arriving.
completedEvery certificate finished without a failure (skipped certificates count as not failed).
partial_failureAt least one certificate failed. See the per-cert breakdown.

There is no failed status and no cancel: a batch in which everything failed still lands in partial_failure, and once submitted a batch runs to completion. Per-certificate results are success, error (with the error message), or skipped — a certificate whose renewal was already in flight from something other than this bulk action.

Idempotency​

The idempotency key is a SHA-256 of the action, the submitting user and the sorted cert-id list. Submitting the same set again while the first action is still pending or in_progress returns the original action, not a new one — this protects against accidental double-clicks and races between API callers. Once the first action has finished (completed or partial_failure), the same selection can be submitted again and starts a fresh action.

# Same set, submitted twice while the first is still running → second returns the original action
curl -X POST $API/bulk-actions \
-H "Authorization: Bearer $TOKEN" \
-d '{"action":"renew","certificate_ids":["a","b","c"]}'
# → {"id":"…","status":"in_progress", …}

curl -X POST $API/bulk-actions -d '…same body…'
# → {"id":"…" (same id), "status":"in_progress", …}

Per-cert tracking​

Each certificate's outcome is recorded exactly once on the action (atomic MongoDB $inc/$push with $slice, deduplicated per certificate), so the counters stay correct under concurrent worker updates. The stored result list is capped; when it overflows, results_truncated is set and the results dialog says so. Bulk-action records expire 90 days after they finish.

Partial failure handling​

When the bulk action finishes in partial_failure:

  • The results dialog lists the failed certificates with their error messages.
  • Each failed renewal also has its own job — open the certificate (or the Jobs page) for the logs.
  • To retry, select the failed certificates and submit Renew Selected again; that is a new bulk action. There is no one-click "retry failed" button.

There is no cancel​

A submitted bulk action runs to completion — the API exposes only create and read status, with no cancel route and no cancelled state. If you need to stop the work, cancel the individual per-certificate jobs from the Jobs page; the bulk action then settles as partial_failure once they finish.

Rate limits​

There is no rate-limit pre-check: CertAutoPilot does not track CA quotas, so a batch that exceeds a CA's weekly limit (for Let's Encrypt, 50 certificates per registered domain per week) fails at the CA for the certificates over the limit. Stagger large batches yourself.

API​

POST /api/v1/projects/{projectId}/bulk-actions
{
"action": "renew",
"certificate_ids": ["cert_a", "cert_b", ...]
}
# → 201 with the bulk action record

GET /api/v1/projects/{projectId}/bulk-actions/{bulkId}
# → {
# "id":"…", "action":"renew",
# "status":"in_progress",
# "total":12, "succeeded":5, "failed":1, "progress_percent":50,
# "results":[ {"certificate_id":"...", "cert_name":"...", "status":"error", "error":"..."} ],
# "results_truncated":false
# }

action accepts only renew; certificate_ids must hold 1–10 000 ids.

Troubleshooting​

Many certificates failed with a CA rate-limit error​

The CA's weekly quota is saturated. Wait for it to roll off, or split the batch over multiple weeks.

Submitting returned an existing action​

The same user already has a running bulk action for exactly this certificate set. Wait for it to finish, or change the selection (adding or removing one certificate changes the idempotency key).

Many certs marked skipped​

A renewal for them was already in flight when the bulk action ran. The skip is safe — no work was duplicated.

See also​

Video tutorial

Short, hands-on videos showing this feature working for real. English audio, English and Turkish subtitles. All video tutorials →

Search, Filter, Bulk Renew and Export CertificatesYouTube ↗