Troubleshooting and Debugging
Instructions for debugging and troubleshooting Swarm Apps
Last updated
Instructions for debugging and troubleshooting Swarm Apps
Last updated
This page documents some features dedicated to debugging Swarm Apps, and presents a few techniques that Authors in the CORE studio have developed over the past few months.
Go to App Page > Analytics Tab. Under Errors you are able to see the errors that occurred when running the app (if any). It is a very useful information that helps authors to debug the app if it is not behaving as expected:
Click on an item to expand and see the details of an error.
The runtime errors are colored in dark grey. They occur when your request breaks the server. Usually that happens when you're missing plugins (see the list of supported plugins here), but that might be caused by other things as well
The errors and warnings in the App's grasshopper definition are colored accordingly and shows which components are throwing an error
Another way of tracking the errors is to use temporary outputs to debug the definition on the cloud.
Let's say for example, when running the definition below we don't get any results back from the server. To localize the issue we added a text output Calc Ratio, that outputs an important piece of data for our definition. Then we run the app again and see if the Calc Ratio returns any data. If it does, it means that the issue is located downstream from that component and we can find and resolve it. When all the issues are resolved, we remove the extra outputs and keep only the desired ones.
We are in alpha, and its entirely possible that you're doing everything right, but that you've hit a wall, or found a bug or something. We want to know! Please reach out on our open Slack channel, or use our feedback form so we can try to help you out.
