We are seeing flow Directory Assistance IN (id 6c5a8f34-b41a-446a-8d98-5ba241a15e34) in our conversation details data but not in our list of flows from /api/v2/flows - does anyone know why this may be occuring?
There's no way to tell why for sure without opening a case with Genesys Cloud Care to inspect your org, but division access is a likely cause.
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.