After submitting a workflow you can go for a coffee and wait for the email notification which is sent by bee. If all went well, then you will receive a success notification, and find your results in the storage system. But in a complex environment, things can go wrong and they sometimes will go wrong. In the remaining part of this section we show some hints how you can troubleshoot your workflow.
If you are using openBIS as storage provide you can use the webclient for checking the status of your processing. Otherwise you can use directly the RESTful interface of the workflow manager.
To get the status of your workflow through the RESTful interface you can use your favorite browser with the address of the workflow manager (which is by default localhost:9999), just use the following address:
where PROCESS_ID is the id you got after submission.
This will return a json object with the status of the workflow and its modules. If you are not familiar with json you can use a json viewer like http://jsonviewer.stack.hu/ into which you can paste in the whole output to see it formatted in a structured way.
Several things can go wrong when you perform a large scale analysis on a cluster: infrastructure problems (failing nodes, filesystems), data problems, wrong parameters. In the following we give some hints which can help to find the root cause of a problem: