Not completely agree: it's not the same as the logging system of Genesys Engage but, in Genesys Cloud, there's a very nice feature (in my opinion) that is the "Replay mode" within Architect (https://help.genesys.cloud/articles/use-replay-mode-to-troubleshoot-an-architect-flow/).
In a nutshell, you can select an interaction from a list coming from the last N days, using some search keys (typically the conversation id) and some filter in terms of day and hour range. Then you can open that interaction in replay mode and execute it, step by step, viewing variables and the result of data actions.
It's really very useful for troubleshooting of a specific interaction. If you need the same in Genesys Engage, in my opinion, it's more difficult to do. I consider this feature of Genesys Cloud as a very good improvement compared to Engage.
Regards
------------------------------
Giuliano Ferri
Indra Italia
------------------------------
Original Message:
Sent: 04-21-2026 09:52
From: Saugort Dario Garcia
Subject: For those who moved from Genesys Engage to Genesys Cloud: what features do you still miss?
One thing a miss most is the logging Genesys Engage has, could be messy surf in hundred of logs, but after use tech and move most info to searching tools, you could have an insight of any interaction or when an integration fails. Be able to know what, when and why an interaction behave as it is valuable, not only for troubleshooting also to answer operations when they detect issues or have doubts about it.
Genesys Cloud has made a lot of things easier but, it needs a way to let us have insights about:
- why agent B was selected instead agent C
- why a interaction was transfered
- what script used agent C and why
- etc, etc, etc
Regards
SG
------------------------------
Saugort Dario Garcia
Arquitecto de soluciones
------------------------------