Hi Dominik
For me, the Notes level is usually sufficient for standard troubleshooting.
I prefer keeping things simple by using a tiered strategy:
Global Baseline: I keep the organization default at Base. This protects high-volume IVRs from unnecessary logging noise while still capturing routing paths and critical errors.
Flow-Level Overrides: I evaluate each flow's configuration individually based on its needs:
None: I set high-volume flows with heavy interactions to None to minimize processing overhead, temporarily bumping them to Notes or Verbose Notes only when a specific issue needs investigation.
Notes: Used for core business flows where tracking variable states is essential for diagnosing issues.
Verbose Notes / All: Reserved strictly for active debugging on integration/Data Action flows or during the 1–2 week hypercare window post-release.
All (Bot Interactions): I typically reserve the All level for scenarios where I need to analyze detailed message exchanges between a customer and a bot (such as AVA or Voice Bots) --> "What the Client Said --> What the Bot Received?"
Security Check (Crucial): If you elevate to Verbose Notes or All, always ensure sensitive fields (tokens, PII, account numbers) are marked as Secure Variables in Architect so they aren't stored in plain text.
A few extra tips & limits to keep in mind:
1. Genesys Cloud only retains execution logs for 10 days.
2. It only returns 200 execution instances, not necessarily the last 200. But you can change the query used to find the specific interaction you want to track.
3. Flows with more than 350 variables will not display in the Execution Data view (replay journey).
4. JSON, String, and Collection variable types have size limits; if a payload exceeds the threshold, the data won't render in the execution journey.
For more details, you can check these resources:
https://help.genesys.cloud/articles/historical-execution-data-overview/
https://help.genesys.cloud/articles/manage-historical-execution-data/
https://help.genesys.cloud/articles/genesys-cloud-fair-use-policy/
I hope I've helped!!!!
------------------------------
Cristian Rojas
Interacciones Inteligentes S.A.
------------------------------