> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/forms/troubleshooting.md). # Troubleshoot form capture and scheduling Work from the source toward the outcome so you can identify where the journey stopped. ## Nothing appears in Distro Check that the tracker or form SDK loaded on the intended page. Confirm the hostname is allowed, the site is active and consent permits the operation. Enable tracker debug logging for a controlled test. For embedded forms, confirm the supported callback or accessible HTML capture path. A cross-origin iframe may require a deliberate integration. ## A form appears but no run starts Review form acceptance, allowed paths, mapping, workflow publication, On/Off state and workspace live-run availability. Inspect the actual trigger choice; a Distro lead form and a captured external form are different sources. ## A run starts with missing data Read the run input. Check the submitted field names, mapped email, skipped field types and changed-form review state. Add fallback conditions for fields that are legitimately optional. ## The scheduler is missing or empty Confirm the run reached **Show Scheduler**. Check whether the source's own redirect left the page, then inspect the event, host identities, calendars, hours, time off and availability window. ## Submission succeeds but booking does not A form submission is not a confirmed meeting. Inspect the booking attempt and final meeting state. Avoid sending a Booked notification until the booking branch actually completes. See [Workflow logs](/workflows/logs.md) and [Calendars and availability](/scheduling/availability.md). --- # 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 dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.distro.so/forms/troubleshooting.md?ask=&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 `build a script that syncs our docs to a CMS` 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.