Dynamics Community Forum Thread Details

We are experiencing an intermittent issue with the Dynamics 365 Channel Integration Framework (CIF) 1.0 when integrating telephony solution.

Occasionally, the softphone iframe is not rendered at all in the DOM, even though it is expected to remain persistently displayed at all times as part of the CIF 1.0 integration. In those cases, it looks as if Dynamics simply does not load or initialize the CIF container.

Issue description

The telephony integration normally loads correctly inside the CIF iframe.
However, at unpredictable times, the iframe is completely missing from the page, meaning no CIF container is created by Dynamics.
When this happens, our integration is obviously not loaded, but the root cause appears to be that Dynamics does not inject the CIF iframe.
The issue is not reproducible on demand — it happens randomly during normal navigation.
We have confirmed that this is not caused by our code, because the iframe itself is not present in the DOM at all.
Most of the time the integration works as expected.

What we checked

Verified HTML structure when the issue happens: no CIF iframe is present.
Checked console logs: nothing indicating an error in our integration.
Reloading the page usually restores the iframe.

Environment

Dynamics 365 Online
Channel Integration Framework 1.0 (deprecated but still supported)

Questions

Is this a known issue with CIF 1.0 or the Dynamics UCI rendering engine?
Are there any workarounds or recommended settings to ensure the CIF iframe is always loaded?
Is this behavior related to any recent Dynamics updates?
Is there a recommended migration path to mitigate this issue (e.g. CIF 2.0 or other framework adjustments)?

Additional material

We can provide:

DOM snapshots showing the CIF iframe missing
Console logs
Navigation steps when the issue occurred

Any assistance or guidance would be appreciated. This issue impacts our telephony integration reliability for our Dynamics 365 users.

Thank you.

_____

Because a picture can sometimes be more illustrative.

Generally, when everything works as expected:

When we observe the issue, the iframe that is supposed to contain our integration is missing from the DOM :