Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

This page has been translated automatically

We want to provide you with the latest help content in your language as soon as possible. This page has been translated automatically and may contain grammatical errors or inaccuracies. We want this content to be useful to you. Please let us know at the bottom of this page if this information was helpful.

View the original article in Russian: Отладчик расписания

general information

The Schedule Debugger allows you to calculate the approximate time of a job and see the approximate progress of a project on a schedule.

To call the debugger, go to the project schedule menu and select the “Schedule debugger” item.

We advise you not to neglect the schedule debugger, because it is confidence that everything will be done as intended! (smile)

Working with the schedule debugger

Step 1. To enable the debugger to show a more plausible progress of the task, you need to specify in seconds the approximate time for a single project execution. The more accurate the time is, the more accurate the calculations will be.

Step 2. After specifying the project execution time, you need to click the "Calculate" button and wait a few seconds until the debugger displays the approximate progress of the project according to the specified schedule from the beginning of the planned launch until the end of the project execution or the end of the emulation period.

После проведенного расчета отладчик покажет данные хода выполнения проекта в формате: дата выполнения — время выполнения — количество предпринятых попыток. Using the data obtained, you can see how the project schedule will work and understand if its intervals and repetitions are configured correctly.

Keep in mind that when you execute a scheduled job directly, the project execution time may vary and differ from the previously set value in the debugger. Thus, the debugger only shows an approximate progress of the project.

  • No labels