Hi all,
We’re hitting a wall with the IVR migration from PureConnect. The cutover date is fixed for the 12th, so the timeline is getting tight. Most of the skill mapping is done, but the Architect flows aren’t behaving as expected when we try to pull the existing configs.
The system is throwing a 403 Forbidden when calling GET /api/v2/architect/ivrs/{ivrId} for specific legacy blocks. It’s weird because the OAuth client has the full set of permissions, yet some IVR IDs return a valid config while others just fail. This is creating a huge risk for the migration window if we can’t validate the flow logic against the source.
We’ve tried refreshing the tokens and checking the org-level roles. The behavior is inconsistent across different IVR IDs in the same environment. Is there a specific permission for legacy migrated objects that isn’t listed in the standard roles? Does this depend on how the IVR was originally imported from PureConnect?