> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/troubleshooting/connectivity-issues.md).

# Connectivity Issues

### Overview

Connectivity issues prevent Transform from loading, saving, or syncing updates.

Most issues are caused by network restrictions, unstable connections, or blocked browser permissions.

### Key Concepts

* **Timeout**: request fails due to network delays
* **Blocked request**: network policy prevents Transform endpoints from loading
* **Session drop**: connection resets during active work

### How It’s Used

Use this page when pages do not load, saves fail, or repeated sign-outs occur.

Use it during initial rollout to validate network readiness.

### Benefits

* Faster triage of network vs application issues
* Cleaner escalation with evidence that support can act on
* Reduced delivery disruption during governance meetings

### Setup Steps

{% stepper %}
{% step %}

### Check service status

Confirm service status before deeper troubleshooting.

* <https://status.transform.ai/>
  {% endstep %}

{% step %}

### Validate basic network connectivity

1. Confirm general internet access works.
2. Retry Transform in a new browser tab.
3. Test on a second network when possible.
   {% endstep %}

{% step %}

### Validate browser prerequisites

1. Confirm a supported browser is used.
2. Confirm JavaScript and cookies are enabled.
3. Disable aggressive privacy extensions for the Transform domain.

Related: [Browser Compatibility](/getting-started/browser-compatibility.md)
{% endstep %}

{% step %}

### Identify network policy constraints

Common signals include:

* consistent failure on corporate networks only
* failure for one region or office
* repeated request blocks in browser developer tools

Escalate to internal IT with timestamps and affected URLs.
{% endstep %}

{% step %}

### Escalate with evidence

Provide:

* scope (Account, Organization, Project)
* exact error text
* timestamp and time zone
* screenshot with sensitive data redacted
  {% endstep %}
  {% endstepper %}

### Best Practices

* Prefer wired connections for long working sessions.
* Avoid captive portals and unstable guest networks during heavy usage.
* Validate network readiness before enabling Meeting Notetaker features that require microphone permissions.

### Summary

Connectivity issues are resolved fastest by isolating service status, network stability, browser prerequisites, and policy constraints.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.transform.ai/troubleshooting/connectivity-issues.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.