> For the complete documentation index, see [llms.txt](https://docs.highcohesion.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.highcohesion.com/monitoring-streams/resending-data/replicate-event.md). # Replicate Event ## When to use? The replicate event feature is one of the most commonly used error resolution features across the HighCohesion platform. Replicating an Event allows you to edit the payload-in of an existing Event. This feature is commonly used when an Event has failed in the Destination due to faulty data, common issues are: * Faulty postcodes * Faulty characters in text fields (e.g. space/text in phone number field) ## How to use? By entering the Event view page of an Event that has failed, you can easily click the replicate button. On clicking the button a modal window will be loaded with the complete payload-in for the specific Event. From the modal window you can edit the payload data directly based on your needs. When clicking on "Replicate Event" a new Event, with the changes to the payload will be sent directly to the Core of the system to be transformed. You can now go back to the Event list and monitor to ensure the newly created Event is processed OK. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.highcohesion.com/monitoring-streams/resending-data/replicate-event.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.