Duplicate-send protection
Flozari uses unique processing keys and duplicate checks across important workflow operations so repeated events are less likely to produce repeated actions.
The problem
Why this safeguard is needed
Webhooks and background jobs can be delivered or retried more than once. If every repeated event is treated as new, a recipient may receive duplicate messages and the same workflow action may run multiple times.
What this safeguard helps protect
- Recipients from repeated automated actions
- Workflow state during webhook retries
- Credits and event records from accidental double processing
How it works in Flozari
- 1
Incoming events and critical actions receive a stable deduplication or idempotency key.
- 2
Flozari checks whether that key has already been processed.
- 3
Duplicate attempts are ignored, reused, or safely resumed depending on the operation.
Good operating practices
- • Avoid cloning live flows without reviewing their triggers.
- • Use one clear owner for overlapping automations.
- • Investigate repeated webhook events before changing safeguards.
Keep human responsibility in the loop
This control supports safer operations but does not guarantee Meta-policy or legal compliance. Your team remains responsible for consent, content, audience selection, review, and applicable requirements.
Use this safeguard as part of a responsible workflow.
Explore the related feature or return to all AI and safety controls.