Rules history

PreviousSchedule a rule to run automatically NextReverting a rule

Last updated 4 months ago

Was this helpful?

Rules history

DataRules creates a history record each time a rule is run.

To navigate to the history pages, open the Kyloe DataTools menu from the top-left button and expand the 'History' section:

Selecting 'DataRules' will open the DataRules history page. Additionally, once you've set a rule running you'll be taken to the DataRules history page:

In the DataRules history you will see for each rule:

The Name of the rule
The entity against which it was run
The UserID of the user who ran the rule
The date and time of execution - when the rule was started
State shows the current status for the rule
The number of records changed shows the total number of records that were successfully updated.
Failed the number of records that failed to update.

Rules can be in the following states:

Completed: The rule has run successfully, and all possible records have been updated. A rule can run successfully with some failed records, this status simply indicates that the rule itself ran to completion without error.
Running: The rule is currently running and updating the Bullhorn database. Only one rule can be running at any time. Whilst the rule is running a small stop button is available. Clicking this will stop the rule and set the status to 'Stopped'.
NOTE: DataRules updates are processed in batches. Clicking the stop button will not immediately bring the update to a halt. The rule will continue until the current batch is complete.
Stopped: The rule that has been manually stopped. 'No. of records changed/Total' column will show how many of the expected records have so far been updated. Clicking the available play button will resume the rule and allow it to run to completion. There is no way to revert a half-run rule, it must be allowed to run to completion before the revert process becomes available.
Failed: The rule that has not run due to an internal error. This can be down to several causes. Running the same rule again should allow the update to proceed. However, if this occurs frequently, please contact Kyloe Support.

PreviousSchedule a rule to run automatically NextReverting a rule

Last updated 4 months ago

Was this helpful?

DataRules creates a history record each time a rule is run.

To navigate to the history pages, open the Kyloe DataTools menu from the top-left button and expand the 'History' section:

Selecting 'DataRules' will open the DataRules history page. Additionally, once you've set a rule running you'll be taken to the DataRules history page:

In the DataRules history you will see for each rule:

The Name of the rule
The entity against which it was run
The UserID of the user who ran the rule
The date and time of execution - when the rule was started
State shows the current status for the rule
The number of records changed shows the total number of records that were successfully updated.
Failed the number of records that failed to update.

Rules can be in the following states:

Completed: The rule has run successfully, and all possible records have been updated. A rule can run successfully with some failed records, this status simply indicates that the rule itself ran to completion without error.
Running: The rule is currently running and updating the Bullhorn database. Only one rule can be running at any time. Whilst the rule is running a small stop button is available. Clicking this will stop the rule and set the status to 'Stopped'.
NOTE: DataRules updates are processed in batches. Clicking the stop button will not immediately bring the update to a halt. The rule will continue until the current batch is complete.
Stopped: The rule that has been manually stopped. 'No. of records changed/Total' column will show how many of the expected records have so far been updated. Clicking the available play button will resume the rule and allow it to run to completion. There is no way to revert a half-run rule, it must be allowed to run to completion before the revert process becomes available.
Failed: The rule that has not run due to an internal error. This can be down to several causes. Running the same rule again should allow the update to proceed. However, if this occurs frequently, please contact Kyloe Support.
Reverted: The rule that previously ran and has then been subsequently reverted (see ).