Troubleshooting Overview

Derick Larson


Troubleshooting the Kinetic Platform starts with logs. Platform Logs are currently available from all four of the components (Request, Task, BridgeHub, and FileHub) in separate locations, and there are web server logs that can also be helpful.

Each platform component has it's own independant logs and ways that they can be interpreted. There are also settings within some of the applications to increase the amount of information contained within the various logs.

Application logs for Request: ce logs basic

And More

Beyond the logs, there are browser developer tools that can help with UI issues like forms or consoles, in-application error handling for workflow errors and webhook errors, and in-application testing capabilitys for bridge-hub.

For workflow problems you may need to look at the application you are integrating with for the logs. For example you have a node on a task tree that is calling a REST API, and you are getting errors back from that service.

The other thing to always be aware of when troubleshooting is what changed. Changes don't have to be in the Kinetic Platform. Environmental changes like updates to software, networks or hardware can cause issues with many different applications.