Checkpoint
This activity is used to record the execution time of parts of the scenario and is used by the BCC's slowdown mechanism.
Time information is sent to the database each time the scenario reaches Checkpoint. Thanks to this, BCC can see the time of task execution (completion of part of a scenario: between checkpoints or start point and first checkpoint or last checkpoint and end of the scenario). When executing the same task multiple times, the slowdown mechanism can calculate the average execution time for that task, and when it begins to significantly exceed this value, the slowdown mechanism reacts and slows down the execution of the scenario. This may be the case when the scenario uses shared resources that are temporarily very busy.
NOTE: Checkpoint should be inserted into the scenario in such a place that it is possible to assess the time of the task execution (e.g. it should be set inside the loop, which will allow to calculate the average execution time of the loop, regardless of the number of its repetitions).
| Parameter Name | Parameter Type | In/Out | Description |
|---|---|---|---|
| Alternative Scenario If Failed | Boolean | Input | checkbox; default is "on" |
| Checkpoint ID | String | Input | checkpoint ID |
| Display Name | Literal | Input | you can change the name of activity for greater clarity of the scenario |
| Exclude from Transaction Check | Boolean | Input | checkbox; default is "off" |
| Result | Boolean | Output | returns the Boolean value: it will return True if no error is in activity, otherwise it will return False |
| Result Code | Int32 | Output | Result Code will return 0 if there is no error in activity, otherwise in most cases it will return 1, the extended result code will show only in several chosen activities |