The command you send must match the type of ETL failure The batch process can only be resumed when it has stopped in a failed state because of its ETL (extract, transform, load) step, and the command you send must match that failure. A mismatched command returns 400 Bad Request with Cannot resume daily — it is not in correct state for resume.

The ResumeETLFailedDaily endpoint lets you resume your tenant's batch process after it has stopped due to an ETL failure, without waiting for manual intervention. Depending on the command you send, Optimove either retries the failed ETL action or skips it, so the rest of the batch process can complete.

Unlike TriggerDaily, this endpoint does not start a new run — it continues the existing failed run from the point of failure. The endpoint is protected by API key authentication, role-based authorization, and per-tenant rate limiting.

For triggering a batch process that has not yet run today, see the Batch Process Trigger Daily API guide.

Beta This capability is in Beta and must be enabled for your tenant before you can use it.

Using the ResumeETLFailedDaily Endpoint

Endpoint

POST <BASE_URL>/BatchProcessAPI/ResumeETLFailedDaily

Replace <BASE_URL> with the base URL for your region.

For the regional base URLs (hostnames), see General Information.

Authentication

API key authentication is required. Include your key in the request header:

If the key is missing or invalid, the endpoint returns 401 Unauthorized.

Authorization

Access is controlled by the role attached to the API key. Callers with the 3rdParty role are explicitly blocked.

Rate Limiting

A per-tenant rate limit applies to all API-key-authenticated requests:

• Window: 600 seconds (10 minutes).
• Only one request per tenant is allowed within the window.
• Exceeding the limit returns 429 Too Many Requests. Wait for the current 10-minute window to expire before retrying.

Request Body Parameters

Content-Type: application/json

The request body must be minified (compact) JSON, with no spaces. A request that is not minified will fail.

{"CommandName":"ResumeTask"}

Here's a breakdown of the request body parameters:

CommandName is the only parameter this endpoint accepts.

Unlike TriggerDaily, this endpoint does not accept WaitTimeForValidationSeconds. The validation wait is fixed at 25 seconds server-side — there is no need to send it, and no way to change it.

Choosing a Command

Not sure which command applies? Contact your Optimove representative. A command that does not match the failure type is rejected, and the rejected call still consumes your 10-minute rate-limit window.

Response Codes

Validation Rules

Before resuming the batch process, the endpoint checks the following preconditions. When a condition is not met, it returns 400 Bad Request with the corresponding plain-text error message.

Examples

Example Request

POST <BASE_URL>/BatchProcessAPI/ResumeETLFailedDaily HTTP/1.1
X-API-KEY: <YOUR_API_KEY>
Content-Type: application/json

{"CommandName":"ResumeTask"}

Example Response (Success)

HTTP/1.1 200 OK
Content-Type: text/plain; charset=utf-8

(empty body)

Example Response (Validation Error)

HTTP/1.1 400 Bad Request
Content-Type: text/plain; charset=utf-8

Cannot resume daily — it is not in correct state for resume

Notes & Best Practices

• Match the command to the failure. Use ResumeTask when the underlying data issue has been fixed and the ETL step should run again. Use ResumeSkipETLTask when the ETL failed with a Data Not Updated error and the run should continue with the ETL action skipped. A command that does not match the failure is rejected.
• A rejected command costs you the rate-limit window. Only one request per tenant is accepted per 600-second window, and a 400 still counts against it. Confirm the failure type before you call, rather than trying one command and then the other.
• CommandName is the only parameter. Do not send WaitTimeForValidationSeconds — the 25-second validation wait is fixed server-side.
• Minify the payload. The request body must contain no spaces: {"CommandName":"ResumeTask"}.
• Empty body on success. On success, the response body is empty (200 OK). Only validation failures return a plain-text message body.
• The call triggers the resume; it does not wait for the run to finish. A 200 OK confirms the resume started, not that the batch process completed. Monitor the run through your usual Optimove monitoring channels.
• Not enabled by default. Contact your Optimove representative to confirm whether this endpoint is enabled for your tenant.

To trigger a batch process that has not yet run today rather than resume a failed one, see the Batch Process Trigger Daily API guide.