Skip to end of metadata
Go to start of metadata

Introduction

When an operation is executed, an operation log is generated. An operation log contains information about when and where an operation ran, the operation status, the number of source and target records processed, and any log messages. Whether detailed log messages are displayed depends on permission and access levels and whether cloud logging is enabled.

Operation logs, including detailed log messages from both Cloud Agents and Private Agents, are retained for 30 days by Jitterbit Harmony.

Operation logs can also be viewed on the Management Console Activities page.

Accessing Operation Logs

Operation logs can be accessed in 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 executed in a project, in a particular workflow, or for a particular operation, respectively. If operations are linked with operation actions, logs for downstream operations are also included.

By Project

The View Logs options for a project, which shows logs for operations that have been executed within a project, can be accessed from these locations:

By Workflow

The View Logs option for a workflow, which shows logs for operations that have been executed within a particular workflow, can be accessed from the project pane's Workflows tab (see Workflow Actions Menu in Project Pane Workflows Tab).

By Operation

The View Logs option for an operation is accessible from these locations:

In addition, after running an operation manually, you can click the operation status on the design canvas to display the logs (see Operation Status in Operation Deployment and Execution).

Viewing Operation Logs

When accessed by workflow or project, the operation log screen loads in the current active tab. When accessed by operation, the operation log screen opens in a new tab for each operation and auto-refreshes if operations are re-run. The tab closes automatically when you close the project (including when switching to another project).

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.

Parent operations (and any child operations beneath them) are sorted in ascending order by Time Started. You can limit the information displayed in the table by filtering or searching.

A maximum of 250 operation logs are displayed. To view additional logs, adjust the filters accordingly, or use the Management Console Activities page, which does not have the 250-log limit.

TIP: Basic configuration of what is included in an operation log is specified under the Options tab of the operation settings (see Operation Options). For more advanced information about other logging options, see Operation Debug Logging for Private Agents.

Filtering by Timeframe

By default, the Start Time Range is configured so that the past 24 hours of logs since last running an operation 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:

To change the timeframe by which the logs are filtered, click within a Start Time Range field to open the date/time picker. Then use the controls within the picker to adjust the date and/or time:

  • Month: The current month is used by default. Use the arrows   to navigate to a different month.
  • Year: The current year is used by default. Click the year, and then use the arrows   to navigate to a different year. Then select the desired month of the year from the month picker. Selecting a month returns you to the date/time picker.

  • Day: Select the desired day from the calendar.
  • Time: Use the sliders to adjust the hour (top slider) and minutes (bottom slider).

Refreshing Logs

The initial logs are displayed based on the date and time that the last operation was run, as displayed at the top of the table. Logs are automatically refreshed every five seconds if any operation is still in a running state (status of Received, Submitted, Pending, or Running). The date and time that the view was last refreshed are reported below the Start Time Range:

You can also manually refresh the logs at any time to display updated information. To manually refresh the logs, click Refresh along the top right:

Filtering by Status

To filter logs by operation status, use the dropdown along the top right:

  • All: All operations are displayed regardless of status.
  • Error: If the agent completes the execution of an operation, but there was a fatal error in writing to the target system, or there was a fatal validation error in the transformation, or the transformation logic triggered the RaiseError function, then the operation status is set to Error and the operation execution terminates.
  • SOAP Fault: If the agent completes the execution of an operation, and the outcome was a SOAP fault, then the status is set to SOAP Fault. This status is applicable only for operations using Salesforce, Salesforce Service CloudServiceMax, SOAP, or Workday activities.
  • Submitted: When operations are submitted to the Harmony queue, but have yet to be picked up by an agent for execution, they have a Submitted status. Operations can be submitted by several means:
    • Jitterbit scheduling service or external scheduling service
    • Manual execution of the operation in Cloud Studio
    • RunOperation function from a script or transformation
    • Any tool, including JitterbitUtils, that calls the Jitterbit Harmony API
  • Received: Once an agent is picked and the agent has acknowledged that it has received the request to run an operation, the status is changed to Received.
  • Pending: Once an operation is scheduled to run in an agent's operation engine, the status is changed to Pending. Operations should not be in Pending status for long durations, as agents should pick up the request and start running operations in a short amount of time.
  • Running: Once the agent starts executing an operation, the status should change to Running. Operations remain in this status until they complete or they encounter an error. The agent starts logging messages generated by the operation as it runs so that users can track which part of the operation is currently being executed.
  • Cancel Requested: If a user wants to stop an operation that is in Submitted, ReceivedPending, or Running status, they can do so from the Activities page of the Management Console. Alternatively, they can enable another operation to cancel an operation using a combination of the GetOperationQueue and CancelOperation functions. Once a cancel is requested, the operation status changes 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.
  • Canceled: Once an agent cancels an operation, it sets the status to Canceled and the operation is terminated. All log information up to the point of cancellation is available for review in the log messages so you know at which point the operation was canceled.
  • Success: Once an agent completes the execution of an operation, if the outcome was a success without warnings from the target system, or warning written in the transformation using the WriteToOperationLog function, then the status is set to Success.
  • Success with Info: If the agent completes the execution of an operation, but there were non-fatal issues in the transformation or posting to the target system or the 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.
  • Success with Warning: If the agent completes the execution of an operation, but there were non-fatal issues in the transformation or posting to the target system, and there was a warning, then the status is set to Success with Warning. This alerts the user to check for warnings in the log messages.
  • Success with Child Error: If the agent completes the successful execution of an operation, but within one or more child operations, there was a fatal error in writing to the target system, or there was a fatal validation error in the transformation, or the transformation logic triggered the RaiseError function, then the operation status is set to Success with Child Error. This status does not apply to asynchronous operations.
  • Delayed Status: If the agent does not return an operation log for any reason, Delayed Status is displayed. Harmony will attempt to fetch logs six times, with a 10-second timeout between each call. Refresh or check the logs again later.

Searching within Logs

Click the search icon  to show a search box for entering keywords in the specified format to be searched for within the operation log screen.

A percent symbol (%) can be used as a wildcard at the beginning and/or end of a keyword.

By Project or Workflow

When viewing logs for the entire project or for a workflow, you can search by operation name or by message within the operation log screen:

  • Operation: Searches by operation name must be specified in the format of operation=keyword.
  • Message: Searches by message must be specified in the format of message=keyword.

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 are returned that match both the operation keyword and the message keyword.

By Operation

When viewing logs for a single operation, you can search by operation log message only:

  • Message: Searches by message must be specified in the format of message=keyword.
TIP: For additional log search capabilities, you can also view logs through the Activities page of the Management Console.

Viewing Logs

The operation logs table includes the columns described below. The table can be sorted (for top-level operations only) by Name, Time Started, Time Done, or Duration by clicking the respective header row. Child operations always appear under their parent operations in the order in which they were executed.

  • Name: The operation name. Parent operations show disclosure triangles  , which can be clicked to collapse or expand child operations.
  • Input/Output: A graphical representation of the current operation. Hover anywhere on the operation row to show a log icon , which can be clicked to show or hide the log for that operation:

    • Source Records: A count of records that have been read from the source system.
    • Target Records: A count of records that have been posted to the target system.
    • Log Messages: Log messages include the log details for the selected operation. Whether log messages are displayed depends on the current user's permissions and access levels and whether cloud logging is enabled. For more information, see the section Log Messages in the Management Console Activities page documentation.

      Under certain circumstances, a Try Again button button may be displayed, covered in Operation Retry, below.

      NOTE: Dates and times displayed within the log messages themselves are not converted to local browser time, but are reported in their original format from the source of the log message.
    • Copy: Click the copy icon  to copy the log data to your clipboard. When clicked, a clipboard icon  is temporarily displayed.
    • Close: Click the close  icon to hide the operation log.
  • Time Started: The date and time the operation began running, displayed as the local browser time.
  • Time Done: The date and time the operation stopped running, displayed as the local browser time.
  • Duration: The time elapsed between Time Started and Time Done.
  • Status: The status of the operation. For a complete list of possible statuses, see Filtering by Status above.

Operation Retry

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 in the operation log.

On clicking Try Again, the project is resynced between the agent and Harmony.

After the resync is complete, the operation run is automatically retried. In cases where a parent or child operation failed, the entire operation chain is retried from the top level down to all downstream operations.

If successful, a success status is 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 Jitterbit Support for assistance).

  • No labels