Logs are available to be viewed directly within Cloud Studio for any operations that have been deployed and executed within a project (see Operation Deployment and Execution). Logs can also be viewed through the Activities page of the Management Console.
|WARNING: For security, logs from agents in a Cloud Agent Group are removed as soon as they are no longer required for an operation to execute properly. In addition, downloading of operation logs through the Management Console Activities page is disabled on agents in a Cloud Agent Group.|
Operation logs can be accessed within Cloud Studio at the project, workflow, or operation level. Depending on where they are accessed, the operation log screen includes logs for all operations that have been deployed and executed within a project, within a particular workflow, or for a particular operation, respectively. If operations are linked with operation actions, logs for downstream operations are also included.
Project Index Card View: Click the project card tile to enter card view. Then hover over a project card and click the actions menu icon to open the actions menu. From the menu, select Logs.
Project Index List View: Click the project list tile to enter list view. Then hover over the empty cell in the column labeled with an actions menu icon and click the additional actions menu icon to open the actions menu. From the menu, select Logs.
Project Pane: Click the actions menu icon to open the actions menu. From the menu, select View Logs.
Logs can be accessed for operations that have been executed within a particular workflow from the project pane in the Workflows tab. Hover over a workflow name and click the actions menu icon to open the actions menu. From the menu, select View Logs.
Project Pane: In the Workflows or Components tab of the project pane, hover over an operation name and click the actions menu icon to open the actions menu. From the menu, select View Logs.
Design Canvas: In the top right of an operation, hover over the actions menu icon to open the actions menu. From the menu, select View Logs. Or, after running an operation manually, you can access the logs by clicking on the operation status that appears in the lower left of the operation.
The operation log screen displays a table of operations that have been deployed and executed within the selected project or workflow, or for a specific operation (see Operation Deployment and Execution). If operations are linked with operation actions, logs for downstream operations are also included. A maximum of 250 operation logs are displayed.
Child operation logs are sorted in the order the operations were executed (that is, by Time Started). You can limit the information displayed in the table by filtering or searching.
|TIP: Basic configuration of what is included in the operation log is specified under the Options tab of the operation settings (see Operation Options). For more advanced information about other logging options, see Enabling Debug Logging.|
By default, the Start Time Range is configured so that the past 24 hours of logs are shown:
The date and time for time range selection uses local browser time. Hover over the Start Time Range tooltip to see the local browser time zone:
There are several ways to change the timeframe by which the logs are filtered:
The initial logs are displayed based on the date and time that the log screen was opened, as displayed at the top of the table. Logs will be automatically refreshed every five seconds if any operation is still in a running state (status of Received, Submitted, Pending, or Running). You can also manually refresh the logs at any time to display updated information.
To manually refresh the logs, click Refresh:
Upon clicking Refresh, the ending timeframe of the log will be reset to the current date and time.
To filter logs by operation status, use the dropdown at the top of the table. The filter is currently limited to select statuses. All possible statuses that may be displayed in the table are listed below.
RaiseError()function, then the operation status is set to Error and the operation execution terminates.
RunOperation()function from a script or transformation
JitterbitUtils, that calls the Jitterbit Harmony API
CancelOperation()functions. Once a cancel is requested, the operation status will change to Cancel Requested. An operation should not remain in this status for long, as the agent should cancel the operation in a fairly short period of time.
WriteToOperationLog()function, then the status is set to Success.
WriteToOperationLog()function was used to write messages to the log, then the status is set to Success with Info. This alerts the user to check for information in the log messages.
RaiseError()function, then the operation status is set to Success with Child Error. This status does not apply to asynchronous operations.
Click the search icon to expand a search box where you can enter keywords in the specified format that will be searched for within the logs.
A percent symbol (%) can be used as a wildcard at the beginning and/or end of a keyword.
When viewing logs for the entire project or for a workflow, you can search by operation name or by message within the operation log:
Only a single operation keyword and single message keyword are supported. When both an operation keyword and a message keyword are provided, the keywords are treated as a combination; that is, operation logs will be returned that match both the operation keyword and the message keyword.
When viewing logs for a single operation, you can search by operation log message only:
|TIP: For additional log search capabilities, you can also view logs through the Activities page of the Management Console.|
The log table includes the columns described below:
Details: Click the plus icon to expand the log details or the minus icon to close the log details. The log details include the number of source and target records processed and log messages. Under certain circumstances, a Try Again button button may be displayed, covered under Operation Retry, below.
|NOTE: Dates and times displayed within the logs themselves are not converted to local browser time, but are reported in their original format from the source of the log message.|
If an operation fails with an error related to file dependencies, this issue may be resolved by resyncing the project between the agent and Harmony. In this scenario, a Try Again button appears within the operation log:
Upon clicking Try Again, the project will be resynced between the agent and Harmony.
After the resync is complete, the operation run will automatically be retried. In cases where a parent or child operation failed, the entire operation chain will be retried from the top level down to all downstream operations.
If successful, a success status will be displayed in the new operation log. If the operation again fails, additional attempts to synchronize the agent won't help and the reason for the failure may be due to something else (contact support for assistance).
|NOTE: A Harmony Agent that is version 10.1 or higher is required for the operation retry to work. If using a lower agent version, the Try Again button still appears but doesn't function.|