# Preflight Health & Connectivity Check

## Why Drizz Runs a Connectivity Check

Before initiating any test execution, Drizz performs a **preflight connectivity check** to ensure the entire testing environment is fully operational and reliable.

This step validates that all critical dependencies required for deterministic automation are reachable and healthy, including:

1. **Deep link resolution** to confirm seamless app-to-platform communication
2. **Authentication services (Auth0, OpenID, JWKS)** to ensure secure and valid session handling
3. **Core backend services** such as Device Management, Test Management, and WebSocket gateways
4. **Network integrity** including DNS resolution, proxy routing, and HTTPS availability

By verifying these components upfront, Drizz ensures:

1. Tests don’t fail due to infrastructure or network issues
2. Real-time device communication is stable
3. Authentication and authorization flows are correctly configured
4. Test execution starts only when the system is fully ready


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.drizz.dev/getting-started/drizz-desktop-app/drizz-desktop-app-setup/download-and-installation/preflight-health-and-connectivity-check.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.