> For the complete documentation index, see [llms.txt](https://schedulink.io/help-center/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://schedulink.io/help-center/when-somethings-wrong/a-form-wont-open.md).

# A form won't open

The code doesn't work, the link does nothing, or a form times out before it's submitted.

Four causes, and the first one only ever affects your own team.

## 1. You're testing a form on the computer you use Schedulink on

**Use the preview icon on the form.** That shows you exactly what your contacts will see, with no email, no code and no second device. It's the right way to check a form before you send it.

If you'd rather test the real thing by adding yourself as a contact and sending it to yourself, you may hit a browser security warning instead of the form. Something along the lines of "your connection is not private".

That happens because your browser remembers that you log in to Schedulink, and it treats the link in the email more cautiously as a result. Your schools and leagues never log in, so they never see it.

To get past it while testing, open the link on a device or browser you don't use Schedulink on. Your phone is usually the quickest.

We're fixing this properly. In the meantime, preview is the reliable way to check a form.

## 2. They're not a contact on that account

A form opens only for someone already listed as a contact on the account it belongs to. That's what the one-time code checks.

So if your contact forwarded the link to a colleague, the colleague can't get in, however legitimate they are. Add them as a contact on the account and send the form again.

It also fails if they enter a different address from the one on their contact record, such as a personal address instead of their work one.

## 3. The form has expired

Once a form's due date passes, the link stops working. Someone who left it until the following week will find nothing happens.

Open the event, find the form, and send it again.

## 4. It timed out while they were away

A form left open for a long stretch times out, and at the moment it does so without warning. Someone who starts it in the morning, gets pulled away, and comes back after lunch will find they can't submit.

**Their answers aren't lost, as long as they clicked Save.** Saved work stays on the form.

To carry on, they open the link from the email again, enter their address, enter the new code, and pick up where they left off. Anything they saved is still there, and they can finish the rest and submit.

So the advice worth putting in your covering email is: save as you go.

We're improving this, so the timeout warns rather than surprises.

## Still stuck

If none of those fit, get in touch with the account name, the event, and who was trying to open it.


---

# 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://schedulink.io/help-center/when-somethings-wrong/a-form-wont-open.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.
