Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

CTI Heartbeat does not start after "HTTP Communication failure"



For a short network or Internet disconnection, when the connection is restored, the CTI browser heartbeat does not beat again. Hence, the server stops monitoring the device after the heartbeat timeout interval (for example, 180 seconds).

Error Messages

Not Applicable

Steps to Reproduce

    1. Log in to the CTI link.
    2. Disconnect from the network for 10 seconds.
    3. Reconnect to the network.
    4. Wait for 180 seconds (use the CTI link normally) before being logged out.

    Root Cause

    A defect in Pegasystems’ code or rules

    Without reaching the maximum heartbeat failures (5), heart beat requests were stopped from being sent.


    Apply HFix-49696.


    Published December 28, 2018 - Updated December 2, 2021

    Was this useful?

    0% found this useful

    Have a question? Get answers now.

    Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

    Did you find this content helpful?

    Want to help us improve this content?

    We'd prefer it if you saw us at our best.

    Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

    Close Deprecation Notice
    Contact us