--- title: "Spring '26 Debugging" slug: "spring-26-debugging" tags: ["Admin", "Compiled from User Guide", "Spring '26", "TMS Admin"] updated: 2026-09-02T14:24:35Z published: 2026-09-02T14:24:35Z canonical: "documents.revenova.com/spring-26-debugging" --- > ## Documentation Index > Fetch the complete documentation index at: https://documents.revenova.com/llms.txt > Use this file to discover all available pages before exploring further. # Spring '26 Debugging ## **Debugging** 1. Logging Enabled 1. Enable if working with Revenova on a technical issue. Displays extra information on the user interface and in the logs for debugging purposes. 2. Logging User 1. The user for which logging is enabled. 3. Enable Packet Replay 1. If *Checked*, it is possible to inject test API JSON or XML responses into the application by saving them as **Files** named after the **API Operation class** for debugging. The Logging User is the recipient of the test response. 4. Retain API Response Packets 1. If *Checked*, this troubleshooting field saves the JSON or XML integration response packets as a file on the associated Load record. Integrations that are not Load-based do not have requests or response packets saved regardless of this field setting. “Push” events from various integrations and any EDI REST API transactions are not supported. 5. Block API Inbound Packets 1. If *Checked*, all inbound integration traffic is blocked by the TMS.