What does the customer connect to receive events?
The customer supplies an endpoint, an address on their own system that accepts messages. Choose what events and fields to send. Use a separate customer configuration for each recipient. Keep the event reference so their system can tell whether it already processed that event.
What should you count and check before replaying?
Current Svix pricing counts attempted messages, with each 64 KiB of payload counted as one message unit. It says filtered messages and retries are free. Check the plan’s limits and history. A second delivery can reach a system that processed the first attempt, so verify how the receiver handles duplicate event references.
What should happen if a fictional order event reaches a customer twice?
Draw one order event and two delivery attempts to the same fictional receiving service.
- Give both attempts the same referenceLabel which attempt the customer already processed.
- Check the business resultWrite the expected one order update and keep each delivery attempt separately in the sketch.