# Monitoring the Workflow The workflow can for instance be monitored by the command `vf_report.sh`. To get information about the workflow in general, within the `tools` folder one can run ``` ./vf_report.sh -c workflow ``` {% hint style="info" %} Please note that the numbers in the ***Ligands*** and ***Dockings*** sections only consider the completed collections. Collections currently in processing are not included yet in these counts. {% endhint %} To get preliminary virtual screening results for the docking scenario *qvina02\_rigid\_receptor1*, one can run the command (within the `tools` folder): ``` ./vf_report.sh -c vs -d qvina02_rigid_receptor1 -n 10 ``` The -n option here specifies that we would also like to have the top 10 compounds listed. \[For more information about monitoring the workflow in general, see the [*corresponding section* ](https://docs.virtual-flow.org/documentation/-LUuXd7bP4jqFNOe_7qQ/using-virtualflow/monitoring)in the documentation.] --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.virtual-flow.org/tutorials-vf1/tutorial-2-vfvs-scratch-bash/monitoring-the-workflow.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.