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

# Troubleshooting

Midio is still in early development, and there will inevitably be bugs. Here is a list of known bugs, and some workarounds.

## Execution error: Failed to consume context

<figure><img src="/files/SsSk7PflCn6DNljlysAR" alt=""><figcaption></figcaption></figure>

This error can occur if you’ve put nodes that either consume or borrow from their execution context inside your own functions. Examples of functions like this include [`Response`](/midio-docs/built-in-nodes/http.md#response) and `Testing.Assert`. You can see what contexts a node requires by hovering its input trigger. See [Contexts](/midio-docs/reference/the-midio-language/contexts.md) for more information, and [Contexts](/midio-docs/reference/the-midio-language/contexts.md#how-it-works) for how you can make your own function use them. The quick fix is to add the EndpointContext to your functions input trigger consumes section.

<figure><img src="/files/RKcxVsIgEegLmTlk4HxC" alt=""><figcaption></figcaption></figure>

## Error notifications when trying to perform edits

This might mean that the editor server or engine has crashed. Try refreshing the browser.

## 502 when sending HTTP request to the editor

This can happen if the URL is malformed, like for example of the port number is not in the right location. Make sure to put the port before the resource part of the url, for example: **https\://\<my-project>.midio.dev:\<port-number>/some/resource**

## Internal error when trying to delete module with types that are referenced from other modules

<figure><img src="/files/gTCyp6h7OUl4o54KBaCt" alt=""><figcaption></figcaption></figure>

The compiler will fail if it is not able to resolve all types, and the editor won’t save changes that cause the compiler to fail. That is why this notification will appear if you try to delete a module with a type that is in use by functions in another module. A workaround until we streamline this case is to first change all uses of that type to another type first, and then try again.