Available translations
loading results
Investigating Issues - Check for Errors at the Browser
Summary: When errors occur in the frontend application, you should either get an on-screen error, or an error should be logged in the browser console.
Open Chrome’s DevTools with the F12 key (when the browser is in focus) and click the Console tab. Then go back to Superalgos and reproduce the issue. The console may display network errors and warnings of different sorts. Those are not important and you may safely ignore them.
Do pay attention to other kinds of errors, such as files that can not be loaded, or errors in specific system components.
Troubleshooting — TOC
You just read page 12 in the topic.
1. How to Troubleshoot an Issue
3. How to Upgrade Your Existing Installation
4. Initial Setup - Node is not Recognized as an Internal or External Command
5. Initial Setup - Superalgos Failed to Connect Via Websockets
6. Perception Issues - My System Gets Slow
7. Perception Issues - There Are No Candles on The Charts
8. Perception Issues - Market Data or Indicators Seem to be Outdated
9. Perception Issues - Indicator Data Seems Wrong
10. Investigating Issues - I Think I Broke Something... How Do I Start Over?
11. Investigating Issues - On-Screen Errors and Warnings
12. Investigating Issues - Check for Errors at the Browser
13. Investigating Issues - Check the Integrity of Your Data
14. Debugging a Task