> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://akamai.ferndocs.com/edge-workers/about-javacript-troubleshooting/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://akamai.ferndocs.com/_mcp/server.
# About JavaScript troubleshooting
In this section you'll find information about debugging, error codes, and how to resolve common errors.
| Option | Description |
| --- | --- |
| [Standard debug headers](/edge-workers/enable-standard-debug-headers) | Provides general status and EdgeWorker information (id, version, and name) for the executed EdgeWorkers function. |
| [Enhanced debug headers](/edge-workers/enable-enhanced-debug-headers) | As a best practice you should enable enhanced debug headers.
You can use DataStream 2 to deliver JavaScript logs. For more information go to the [Use DataStream 2 to deliver JavaScript logs](ds2-javascript-logging.md) tutorial.
These enhanced debug trace headers provide actionable details that will help you troubleshoot your EdgeWorkers. |
| [Error codes - EdgeWorkers Management Application](/edge-workers/error-codes) | View a list of error codes that are displayed in the EdgeWorkers Management application to keep you informed about limitations and issues. |
| [Common errors](/edge-workers/common-errors) | Review the common errors and how they can be resolved. |
Review these resources and tips that can also help you troubleshoot and test your EdgeWorkers:
- To handle exceptions cleanly write `try` and `catch` blocks in your JavaScript code.
- Refer to the [Limitations](limitations.md) section for information about what you should keep in mind when designing your EdgeWorkers functions. You can also review a list of the currently supported delivery products.
- Use [Site Failover](site-failover.md) to define what action to take in the event that an EdgeWorkers function fails.
- EdgeWorkers functions are supported on both the Enhanced TLS and Standard TLS networks.