[Home](https://help.qlik.com/en-US/cloud-admin-playbook/Content/home.htm) > [Data integration](https://help.qlik.com/en-US/cloud-admin-playbook/Content/data_integration.htm) > [Data gateways](https://help.qlik.com/en-US/cloud-admin-playbook/Content/data_integration/data_gateways.htm) > Check gateway health

# Check gateway health

**Cadence:** Daily

**Subscription model:** All

**Roles:** Tenant Admin (TA), Data Admin (DA—Data Movement gateways only)

**Last verified:** 2026-09

|  | Initial | Recurring |
| --- | --- | --- |
| **Estimated time** | 5 min | 5 min |

**Benefits:**

* Early detection of gateway disconnection before reloads or data tasks fail
* Confirms notification routing is working as expected
* Quickly surfaces gateways stuck in an **Establishing session** loop (the gateway is reaching Qlik Cloud but failing to connect to its data source)

***

## Goal

> **Applies only if your tenant uses Qlik Data Gateway.** To check: admin console → **Data gateways**. If the page is empty, your tenant reaches data sources directly (or via cloud-native connectors) and this task doesn't apply—skip and move on.

The **Data gateways** page in the admin console lists each Direct Access and Data Movement gateway with version and status. Status values are:

* **Connected**—reachable from Qlik Cloud and ready.
* **Disconnected**—not reachable from Qlik Cloud.
* **Disabled**—administratively turned off.
* **Establishing session**—Qlik's documentation defines this as the state shown
  > when the data gateway establishes a connection to the data source

  ; practically, it indicates that the gateway has reached Qlik Cloud but the downstream data-source leg is still negotiating or failing.

Configure notifications per gateway for status changes. Daily verification confirms the gateways are reachable from Qlik Cloud and that notifications are configured.

## Tasks

| Task | TA | AA | DA | AuA |
| --- | --- | --- | --- | --- |
| Verify all Direct Access gateways are **Connected** | ✓ |  |  |  |
| Verify all Data Movement gateways are **Connected** | ✓ |  | ✓ |  |
| Confirm gateway notifications are configured to email / push for status changes | ✓ |  |  |  |
| For intermittent disconnects, confirm host **NTP is running** and time is within tolerance of the tenant region—clock skew silently drops the mTLS tunnel | ✓ |  | ✓ |  |

## Gotchas

* **`--ca_bundle_path` left on by mistake leaves the gateway permanently offline.** The flag is the supported install path for Qlik Cloud Government tenants and for commercial tenants behind TLS-intercepting proxies (must point at the corporate CA bundle). When investigating a newly installed gateway stuck **Disconnected**, check the install command. If `--ca_bundle_path` is set without an actual TLS-intercepting proxy or QCG trust chain, uninstall and reinstall without the flag.
* **Never delete the registered space of a gateway**—that orphans the gateway and forces re-registration with a new key against a non-disposable space. **From Direct Access v1.8.0**, re-registration can be scripted via automatic command-line registration instead of the admin console, which is worth building into a host-rebuild runbook—see [Gateway host operations](https://help.qlik.com/en-US/cloud-admin-playbook/Content/data_integration/data_gateways/gateway_host_operations.htm).

## Automation helpers

* **Alert Qlik Talend Data Integration server license expiring within X days**—Adjacent license-expiry tracking for Data Movement gateways.

## References

* [Managing Direct Access in Administration](https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Gateways/direct-access-gateway-managing-console.htm)
* [Managing Data Movement gateway in Administration](https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Gateways/dm-gateway-managing-console.htm)
* [Data gateways (overview)](https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Gateways/setting-up-gateways.htm)

**Tags:** `#daily` `#data_integration` `#data_gateways` `#direct_access` `#data_movement`