> You are reading the Docusign Developer Documentation. For clean Markdown of any page, append .md to the page URL.
>
> Documentation indexes by section:
> - APIs and SDKs: https://docusign.docs.buildwithfern.com/docs/llms.txt
> - Platform 101: https://docusign.docs.buildwithfern.com/platform/llms.txt
> - Extension Apps: https://docusign.docs.buildwithfern.com/extension-apps/llms.txt
> - Docusign CLI: https://docusign.docs.buildwithfern.com/docusign-cli/llms.txt
>
> Authentication (OAuth, JWT Grant, M2M): https://docusign.docs.buildwithfern.com/platform/auth
> Webhooks and Connect: https://docusign.docs.buildwithfern.com/platform/webhooks
>
> OpenAPI specifications: https://docusign.docs.buildwithfern.com/openapi.json
> MCP server: https://docusign.docs.buildwithfern.com/_mcp/server

# Go-Live troubleshooting

> Get help with some of the common problems experienced by integrations failing the go-live review.

> **Note**
>
> Have a problem going live with your production account? See [Docusign Support](https://support.docusign.com/s/contactSupport) to open a ticket and get help.

While the rules for Go-Live review are fairly straightforward, passing your review isn’t always so simple. Here are a few common causes of failure, along with guidance on what you can do before and during the [Go-Live process](/platform/go-live) to prevent those causes from blocking a review request:

* **Review expired:** A key in this status had previously undergone review but was not submitted by selecting **Actions** > **Start Go Live**. Unless submitted for processing, the review data only persists for a limited amount of time.
* **OAuth 2.0 required:** Your REST integration must use OAuth 2.0, or you must request a policy exception.

If you are still encountering Go-Live problems, try:

* Downloading the log of the reviewed transactions by selecting **DOWNLOAD LOGS** in the **Review Results** window, then using the contents of the log file to identify and resolve any errors.
* Making sure that your admin console security session has not timed out. Refresh the page or use incognito mode (private browsing) to avoid timeouts.
* Troubleshooting using the [API Dashboard](https://admindemo.docusign.com/authenticate?goTo=developerDashboard). See [API Dashboard overview](/tools/api-dashboard) for details.
* Opening a support case with [Docusign Support](https://support.docusign.com/s/contactSupport) if you have a paid support plan or you are enrolled in the [Docusign Partner Program](https://partners.docusign.com/s/join-now). See [FAQ: Support for developers and Docusign APIs](https://support.docusign.com/s/articles/FAQ-Support-for-developers-and-Docusign-APIs) for details about support plans.

## Next steps

* Review [From the Trenches: Go-Live failures](https://www.docusign.com/blog/developers/the-trenches-go-live-failures) to learn more about common issues that can affect Go-Live review.
* Join the [Docusign Developer Community](https://community.docusign.com/developer-59) to get help from other developers and the Docusign support team.