Execution Log View

On this view, you can see -up to the smallest details- what has happened during the last execution of the current process. The data in this view is overwritten by a new execution round.

Whenever a Djeeni process is executed, this log is written. The next execution of the Djeeni process overwrites the log. Also editing the process clears this log as it is not relevant anymore. In case you want to analyse the results, please check this view right after the execution of the Djeeni process.

Every row on the sheet is a separate entry that consists of the following information about the execution of a process step:

• Column A: Step No: The number of the step within the process according to the Detail Editor. This information is not displayed elsewhere at the moment.
• Column B: Detail Row: The row number of the executed step on the Detail Editor worksheet. You can identify the executed step by this row number.
• Column C: Step Name: The name of the process step as you can see in the Visual and Detail Editor.
• Column D: Status: The status information of the log entry:
  • OK: Confirmation about a successful action within the Step (e.g. a worksheet that should be used is indeed found in the system; the worksheet is opened; data is copied)
  • Notice: Djeeni has made a smaller decision because there was a missing piece of information. Most probably the decision is correct and you do not have to do anything
  • Warning: Djeeni has made a bigger decision because of missing information. The decision is most probably correct but requires attention.
  • Error: Djeeni could not perform an action of the process step. A verbose error description is provided.
• Column E: Message: The log entry text (information / error description)

About a process step (most of the time) several log entries are created. Read them all to understand if something goes differently than expected. Also, pay attention to the fact that certain process steps can be executed several times (inside of a WBook List or Row List) generating log entries for each time the process step is executed.

Djeeni execution stops when Djeeni can not perform an action inside of a process step. An error message is generated and the process execution is aborted. Getting an error at a certain process step does not necessarily mean that the reason behind the error is at that step. Read the log from the beginning and find the first notice or warning. Maybe the decision that was made at the point of the notice of warning caused the error later. Checking and adjusting the settings of the notice/warning step can help Djeeni to execute the process the next time without error.

A quite frequently occurring error that Djeeni stops because it cannot find a worksheet or cell or range that was correctly used or located earlier. Always check the Djeeni name - a typo can be the reason of error.