...
For some projects, the above methods to calculate the progress may not be adequate. For example, a project may have two modes (eg. Full and BugFix). The two different modes may have very different progress totals, and using the last successful run action count method will only work some of the time. You can override the estimated total using a either the script method "SetEstimatedProgressTotal", or by using the Set Build Status Message action.
Running Statistics
This section displays the following information:
Current Running Actions
This section shows the current ActionList as well as a list of all the currently running actions (it is possible to have more than one action running simultaneously using the ASync Action Group)
...
Using the same example above - your project has Full and BugFix modes. You know (because you've run the Full mode enough times) that Full mode will run 469 actions, and that BugFix runs only 210 actions. Your project will have some logic at the start which figures out if Full or BugFix is required, and using that same logic it can call the script function to set the estimated Estimated progress total (in JavaScript):
...