Braze retries a 500: keep the Sume job submit idempotent

Can a Braze retry create two Sume jobs?

It can if your endpoint submits a paid job on every request. Braze's docs say 500 and 502 responses go to its retry logic and that a :retry option exists. A retry reaches your server as a new request, so your code has to recognize it as the same request.

Sume requires an Idempotency-Key on paid POSTs. Derive it from what makes the request unique, such as the campaign id plus the segment, never from the clock or a random value.

What does Braze do with each status?

How do I derive a stable key?

Hash the inputs that define the clip: avatar handle, script, aspect ratio and quality. The same inputs give the same key, and a different script gives a different key. Sume's docs also say not to resubmit the original paid request only because a local process timed out; poll the job instead.

Rather than submitting inside the Connected Content request at all, submit from a background step and have the lookup read the stored URL.

import hashlib, json

def idem_key(campaign, body):
    blob = json.dumps(body, sort_keys=True)
    digest = hashlib.sha256(blob.encode()).hexdigest()[:24]
    return "braze-" + campaign + "-" + digest

body = {"avatar_handle": "your_avatar_handle",
        "script": "Two more days at this price.",
        "aspect_ratio": "9:16", "quality": "standard"}
print(idem_key("bf26", body))

What else should the endpoint do on a retry?

Return 2xx for a request you already accepted, even if the clip is not ready; give the fallback URL in the body. A 429 is also treated by Braze as a failure, so protect your own endpoint from bursts. See retrying with the same key on a 429.