I checked the current Botpress docs, and I don’t see a documented guarantee around webhook ordering, duplicate delivery, retry behavior, or a maximum retry window, so I wouldn’t build the deletion logic around an assumed delivery guarantee. What I’d do on the backend is make the callback idempotent using the Botpress event ID (Botpress events expose an "id" and "conversationId"), persist the final result first, and only delete the Conversation once that write has succeeded. The main thing I’d want to confirm is which Botpress callback mechanism you’re using. If you tell me whether this is the Chat API webhook, a custom event, or a Studio hook, I can narrow down the exact lifecycle and the safest point to trigger the deletion. @delightful-garage-18870