Prompt that stores business data and event intents in one step and makes delivery retryable. Paste it into an AI tool of your choice, which then designs reliable event publishing.
Results depend on the tool, the model and what you enter.
Fill in
What you type stays in this browser window. We store and send nothing.
Which flow?
create order
change account
finish import
status transition
other write
Where does the message go?
queue
partner webhook
email or push
search index
several targets
How does it work today?
store then send
send only
retry without key
manual catch-up
unclear
Your prompt
Help me store business data and outbound events so that after a crash nothing is missing and nothing arrives twice.
Flow: [Flow]
Targets: [Targets]
Today: [Today]
Steps: 1. Read the code that stores business data and then sends events or messages. 2. Mark places where store and send are separate and a crash in between can split data and message. 3. Propose storing event intents in the same transaction as the business data and delivering asynchronously afterwards. 4. Define how delivery retries with an idempotency key and what happens on lasting failure. 5. Check whether consumers can tolerate duplicate delivery. 6. Describe monitoring for unprocessed intents and delayed delivery.
Output: current risks, store-and-deliver design, idempotency rule, failure path and monitoring.
Take particular care to store intent and business data together and make every delivery retryable.
Before you answer, check: Are all instructions met? If key information is missing or a placeholder in square brackets is still in the text, ask instead of guessing. Mark assumptions as assumptions.
You have edited the prompt. Changes in the fields above no longer overwrite it.
This is an instruction for an AI, not the result itself.
Fill in the fields or tap a suggestion. Leave out names, addresses and other personal data.
Copy the finished prompt into an AI tool of your choice.
Paste the write and send code, transaction boundaries and examples of duplicate and loss cases, without real customer data.
Why does this work?
If the app stores the order and crashes before send, the warehouse never hears about it. With the intent in the same transaction, a worker can catch up later.
Tips
Build delivery with intentional duplicate messages first and check that consumers can handle them.
Prompt that plans a data backfill in small, resumable batches with clear brakes.
Prompt · Intermediate · about 15 min
You may use our prompts freely, including at work. Please do not republish them as your own collection. We give no warranty for AI results; check them yourself. Terms of use
