Troubleshooting
Last updated
Was this helpful?
Last updated
Was this helpful?
Midio is still in early development, and there will inevitably be bugs. Here is a list of known bugs, and some workarounds.
This might mean that the editor server or engine has crashed. Try refreshing the browser.
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
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.
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 and Testing.Assert
. You can see what contexts a node requires by hovering its input trigger. See Contexts for more information, and 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.