Understanding Strategy Logs

When working with OneConnect strategies, things usually run smoothly—but occasionally, something might not go as expected. That’s where strategy logs come in.

Strategy logs are detailed records of what happens each time a strategy runs, including what was processed successfully, what didn’t work, and why. These logs were originally designed by and for developers, so they can be technical and a bit overwhelming at first glance. However, they’re also a powerful tool for identifying and resolving issues in your integrations.

This guide is designed to make strategy logs easier to understand for all users—whether or not you have a technical background. We’ll break down what to look for in a log, how to interpret common messages, and how these logs can help you troubleshoot problems more quickly and effectively.

Navigating to the Logs

All strategy logs for an integration can be found within the integration itself. There are three main ways to review your strategy's logs:

Navigate to the Schedules page and select the View Schedule Logs button.

Use the Logs dropdown in the main navigation and select either Events or Schedules.

Types of Strategies

Event-Driven Strategies

Event-Driven Strategies are triggered by specific actions, such as clicking the import button in the Connected Systems screen of OnePlan.

Key characteristics:

You may need to provide an Item ID (e.g., a Plan ID from OnePlan or a related ID from another system).
The strategy processes all mapped data related to the specific item.
Event logs offer detailed insights, making them especially helpful for diagnosing persistent issues.

Examples:

OnePlanPublish events use a Plan ID from OnePlan as the source.
OnePlanUpdate events use an equivalent ID from another program.

Not all strategies support event-based execution. Refer to your integration's documentation to confirm compatibility.

Scheduled Strategies

Scheduled strategies run automatically at defined intervals or can be triggered manually.

Types of execution:

Automatic Runs: Strategies execute based on a preconfigured schedule. This functionality is not available for integrations using a Basic license.
Manual Runs: You can manually run a strategy by clicking the Execute Strategy button (lightning bolt icon). In this case, no Item ID is required.

Anatomy of the Log Details Form

To view the details of a specific strategy from the Logs page, click the View Details link for the strategy you're interested in, and the Log Details form will open.

This form is broken into three main sections: Generic Info, Payload Info, and Logging Info.

Log Details minimal.png

Generic Info

This section provides a high-level overview of the strategy run. It includes:

Strategy name
Creation date
Start time
Last updated time
Current state
Status
Percent Complete

These fields are useful for quickly assessing the current state of a strategy - whether it is still processing or has completed - and for reviewing basic execution metadata.

Payload Info

The Payload Info section outlines what triggered the strategy and includes key data required for execution. This information varies depending on the trigger type.

Event-triggered from OnePlan: Specific item data (e.g., Plan ID) is included.
Automatically triggered by OneConnect: Broader parameters or global queries may appear.

A few important notes:

If the itemid field displays an asterisk (*), this indicates that all data is being queried from the external program.
If specific IDs are listed, only those items are being processed.

Log Details Payload.png

Logging Info

This is the most detailed and diagnostic section of the Log Details form.

It shows a step-by-step breakdown of the strategy's execution, including:

What delta types are applied
Which filters are in place
The functions used to process the data

This section is particularly valuable for debugging and understanding where in the process something may have gone wrong.

Simple vs Detailed View

When a strategy is run as part of a scheduled execution, the logs will default to Simple view. This view provides a streamlined overview of the strategy's processing without showing internal processing functions for each item.

Simple View Overview:

Pre-processing logs (initial steps) are displayed by default.
Once item-level processing begins, the logs show only Start and Finish timestamps for each item, along with any error messages related to that item.
This view is ideal for high-level monitoring of success/failure states.

Example of a successful Simple view of items being processed:

6/5/2025 5:38:13 PM (PST): Executing
6/5/2025 5:38:14 PM (PST): ITEM (0): 24 START
6/5/2025 5:38:29 PM (PST): ITEM (0): 24 FINISH 00:00:14.882
6/5/2025 5:38:29 PM (PST): ITEM (1): 36558 START
6/5/2025 5:38:32 PM (PST): ITEM (1): 36558 FINISH 00:00:03.128
6/5/2025 5:38:32 PM (PST): COMPLETE: SUCCESS

Error Display in Simple View

If an item encounters an error during processing, the error is listed at the bottom of the log. The summary view still shows all items processed, with errors called out after completion.

Example of an error occurring on a single item when multiple items are being processed in Simple view:

6/12/2025 10:53:43 AM (PST): Executing
6/12/2025 10:53:54 AM (PST): ITEM (0): 2 START
6/12/2025 10:59:15 AM (PST): ITEM (0): 2 FINISH 00:05:21.388
6/12/2025 10:59:15 AM (PST): ITEM (1): 3 START
6/12/2025 11:04:32 AM (PST): ITEM (1): 3 FINISH 00:05:16.822
6/12/2025 11:04:32 AM (PST): ITEM (2): 8 START
6/12/2025 11:07:11 AM (PST): ITEM (2): 8 FINISH 00:02:38.612
6/12/2025 11:07:11 AM (PST): ITEM (3): 9 START
6/12/2025 11:09:36 AM (PST): ITEM (3): 9 FINISH 00:02:24.937
6/12/2025 11:09:36 AM (PST): ITEM (4): 21 START
6/12/2025 11:16:01 AM (PST): ITEM (4): 21 FINISH 00:06:25.575
6/12/2025 11:16:01 AM (PST): ITEM (5): 25 START
6/12/2025 11:21:25 AM (PST): ITEM (5): 25 FINISH 00:05:23.942
6/12/2025 11:21:25 AM (PST): ITEM (6): 32 START
6/12/2025 11:23:40 AM (PST): ITEM (6): 32 FINISH 00:02:14.177
6/12/2025 11:23:40 AM (PST): ITEM (7): 33 START
6/12/2025 11:29:57 AM (PST): ITEM (7): 33 FINISH 00:06:16.981
6/12/2025 11:30:07 AM (PST): ITEM (8): 34 START
6/12/2025 11:30:54 AM (PST): ITEM (8): 34 FINISH 00:00:47.269
6/12/2025 11:30:54 AM (PST): ITEM (9): 40 START
6/12/2025 11:31:30 AM (PST): ITEM (9): 40 FINISH 00:00:35.344
6/12/2025 11:31:30 AM (PST): ITEM (10): 41 START
6/12/2025 11:32:40 AM (PST): ITEM (10): 41 FINISH 00:01:10.696
6/12/2025 11:32:40 AM (PST): ITEM (11): 44 START
6/12/2025 11:33:54 AM (PST): ITEM (11): 44 FINISH 00:01:13.629
6/12/2025 11:33:54 AM (PST): ITEM (12): 45 START
6/12/2025 11:34:14 AM (PST): ITEM (12): 45 FINISH 00:00:20.386
6/12/2025 11:34:15 AM (PST): ITEM (13): 46 START
6/12/2025 11:34:35 AM (PST): ITEM (13): 46 FINISH 00:00:20.678
6/12/2025 12:15:43 PM (PST): ITEM (9) [StampPropertiesInformation]: Error: The remote server returned an error: (500) Internal Server Error. Status: ProtocolError QueryUrl: https://oneplanqagraph.azurewebsites.net/api/integration/updateplanintegrationproperties?PlanId=a4f40483-9bf0-4a3d-9121-6f2742e0aa8c

Detailed View

If further troubleshooting or item-level transparency is needed, toggling Detailed View will reveal:

Each function executed for every item
Specific filter logic
Transform steps
Errors with full context and message paths

This view is particularly useful when:

An item fails consistently across multiple runs
All items fail with similar errors
You need to trace how data was handled during processing

What Happens Before Data Is Processed

Before any item-level processing begins, the strategy enters an initialization phase. This prepares the data pipeline and determines what data should be retrieved and processed.

Typical early log entries include:

Initializing: Signals the start of execution
Deltas: Displays the timestamp for incremental data queries
STEP entries: Show the execution of core strategy stages such as querying, translation, filtering, and scheduling

Example of what some logs may look like prior to data processing:

6/12/2025 10:50:05 AM (PST): Initializing
6/12/2025 10:50:11 AM (PST): Deltas (Incremental): 6/10/2025 9:12 PM (UTC)
6/12/2025 10:50:11 AM (PST): Executing
6/12/2025 10:51:54 AM (PST): STEP (0): GetAllWorkItems ON Destination START
6/12/2025 10:51:57 AM (PST): 32 work item(s) retrieved
6/12/2025 10:51:59 AM (PST): PAGE (1): No work items retrieved
6/12/2025 10:51:59 AM (PST): STEP (0): GetAllWorkItems ON Destination FINISH (SUCCESS) 00:00:05.337
6/12/2025 10:51:59 AM (PST): STEP (1): Translate ON System START
6/12/2025 10:51:59 AM (PST): STEP (1): Translate ON System FINISH (SUCCESS) 00:00:00.123
6/12/2025 10:51:59 AM (PST): STEP (2): Filter ON System START
6/12/2025 10:52:00 AM (PST): Filtering skipped: No expression found.
6/12/2025 10:52:00 AM (PST): STEP (2): Filter ON System FINISH (SUCCESS) 00:00:00.119
6/12/2025 10:52:00 AM (PST): STEP (3): Schedule ON System START
6/12/2025 10:52:00 AM (PST): Queuing 32 Items
6/12/2025 10:52:00 AM (PST): STEP (3): Schedule ON System FINISH (SUCCESS) 00:00:00.121
6/12/2025 10:52:00 AM (PST): Queued 32 Items
6/12/2025 10:53:01 AM (PST): Initializing

These entries help clarify how data is gathered, filtered, and prepared before processing begins.

Deltas & Filtering: Why Some Data Doesn’t Get Processed

Not all data pulled into an integration strategy will be processed or transferred. This is typically due to one of two reasons: delta settings or filters. Both mechanisms help make sure only the right data gets processed—cutting down on clutter, boosting efficiency, and keeping things running smoothly.

Incremental Deltas

Integration strategies can be configured with either full or incremental delta logic:

Full Deltas: All available data is transferred, regardless of when it was last modified. This method is thorough but may slow down performance due to the large volume of data.
Incremental Deltas: Only data that has changed since the last successful strategy run (or some other date that is configured for the strategy) will be processed. This is faster and more efficient, and it's the most common approach for scheduled or recurring strategies.

Delta configurations are typically set at the strategy level. Information on strategies can be found here.

Filters

Once data is retrieved, filters further reduce it to only what is relevant for the integration. These are usually defined at the plan level, and apply after the data has been pulled from the source system.

This means that even if thousands of records are retrieved, only a small number may actually proceed through the pipeline if they match the filter criteria.

Example of a filter being applied after data has been gathered:

6/5/2025 5:37:06 PM (PST): STEP (0): GetAllWorkItems ON Destination START
6/5/2025 5:37:08 PM (PST): 200 work item(s) retrieved
6/5/2025 5:37:09 PM (PST): PAGE (1): 200 work item(s) retrieved
6/5/2025 5:37:11 PM (PST): PAGE (2): 200 work item(s) retrieved
6/5/2025 5:37:12 PM (PST): PAGE (3): 200 work item(s) retrieved
6/5/2025 5:37:13 PM (PST): PAGE (4): 200 work item(s) retrieved
6/5/2025 5:37:15 PM (PST): PAGE (5): 200 work item(s) retrieved
6/5/2025 5:37:16 PM (PST): PAGE (6): 200 work item(s) retrieved
6/5/2025 5:37:18 PM (PST): PAGE (7): 200 work item(s) retrieved
6/5/2025 5:37:19 PM (PST): PAGE (8): 200 work item(s) retrieved
6/5/2025 5:37:21 PM (PST): PAGE (9): 200 work item(s) retrieved
6/5/2025 5:37:22 PM (PST): PAGE (10): 200 work item(s) retrieved
6/5/2025 5:37:23 PM (PST): PAGE (11): 200 work item(s) retrieved
6/5/2025 5:37:25 PM (PST): PAGE (12): 200 work item(s) retrieved
6/5/2025 5:37:26 PM (PST): PAGE (13): 200 work item(s) retrieved
6/5/2025 5:37:28 PM (PST): PAGE (14): 200 work item(s) retrieved
6/5/2025 5:37:29 PM (PST): PAGE (15): 200 work item(s) retrieved
6/5/2025 5:37:30 PM (PST): PAGE (16): 200 work item(s) retrieved
6/5/2025 5:37:32 PM (PST): PAGE (17): 20 work item(s) retrieved
6/5/2025 5:37:33 PM (PST): PAGE (18): No work items retrieved
6/5/2025 5:37:33 PM (PST): STEP (0): GetAllWorkItems ON Destination FINISH (SUCCESS) 00:00:27.273
6/5/2025 5:37:33 PM (PST): STEP (1): Translate ON System START
6/5/2025 5:37:33 PM (PST): STEP (1): Translate ON System FINISH (SUCCESS) 00:00:00.211
6/5/2025 5:37:33 PM (PST): STEP (2): Filter ON System START
6/5/2025 5:37:33 PM (PST): Filtering: [MapId] <> '' AND [Id] <> ''
  Selected: 2 of 3420
6/5/2025 5:37:33 PM (PST): STEP (2): Filter ON System FINISH (SUCCESS) 00:00:00.132

In this case, although over 3,400 items were retrieved, only 2 matched the filter logic and continued through the pipeline.

Filter logic is customizable, information on strategy filters can be found here.

Data Processing: Functions and Common Operations

Anatomy of log entries

Each new entry in the strategy logs begins with a timestamp. The time zone is determined by your OneConnect group settings and applies to all users in that group reviewing logs.

After the timestamp, the log will display messages, steps, or functions that the strategy is processing.

Steps listed in the format:

STEP (#): [Function Name] ON [System]

Each step will have a START and a FINISH entry, indicating the beginning and completion of that function. The FINISH entry will include a status (SUCCESS, ERROR, SKIP or END) and the duration of the step.

Example of a Successful function:

6/5/2025 5:38:14 PM (PST): STEP (0): GetEachWorkItem ON Destination START
6/5/2025 5:38:14 PM (PST): STEP (0): GetEachWorkItem ON Destination FINISH (SUCCESS) 00:00:00.215

Example of a Failed function:

6/5/2025 5:18:41 PM (PST): STEP (4): FilterPlansByIntegration ON Source START
6/5/2025 5:18:41 PM (PST): The [Team Projects Areas] field is not mapped. Please map the field. Refer to the online help for instructions.
6/5/2025 5:18:41 PM (PST): STEP (4): FilterPlansByIntegration ON Source FINISH (ERROR) 00:00:00.105

Deciphering log entries

Example of what a successful detailed log may look like for a single item:

6/5/2025 5:38:14 PM (PST): ITEM (0): 24 START
6/5/2025 5:38:14 PM (PST): STEP (0): GetEachWorkItem ON Destination START
6/5/2025 5:38:14 PM (PST): STEP (0): GetEachWorkItem ON Destination FINISH (SUCCESS) 00:00:00.215
6/5/2025 5:38:14 PM (PST): STEP (1): Translate ON System START
...
6/5/2025 5:38:22 PM (PST): STEP (26): BulkUpsertTasks ON Source START
6/5/2025 5:38:23 PM (PST): Backlog import job has been successfully scheduled items in the server.
Queued: 7
Skipped: 0
6/5/2025 5:38:23 PM (PST): STEP (26): BulkUpsertTasks ON Source FINISH (SUCCESS) 00:00:01.297
6/5/2025 5:38:23 PM (PST): STEP (27): GetProcessedInfo ON Source START
6/5/2025 5:38:29 PM (PST):
INFO: ProcessId 9b0e1cd6-3702-4e50-a9e1-b1eeb534123e attempt #1/60. Key: 'xxxxxIo'. Response Code: '200'
INFO: ProcessId 9b0e1cd6-3702-4e50-a9e1-b1eeb534123e attempt #2/60. Key: 'xxxxxIo'. Response Code: '200'
Starting

Number of Work Plan Items to process: 7
Work Plan Item Type: Backlog
Work Plan Items Removed (Deleted): 0
Process: Auto Import Resource Planner (Started)
Process: Auto Import Resource Planner (Completed)

OneConnect Item Mappings to Create: 0
OneConnect Item Mappings to Delete: 0
Created: 0
Updated: 7

Work plan items have been imported successfully.
6/5/2025 5:38:29 PM (PST): STEP (27): GetProcessedInfo ON Source FINISH (SUCCESS) 00:00:05.248
6/5/2025 5:38:29 PM (PST): ITEM (0): 24 FINISH 00:00:14.882

Throughout the log:

Each STEP shows the function name and where it runs (System, Source, Destination or Integrator).
Extra messages between steps may offer additional insights, like:
- Messages (e.g., "Filtering skipped: No expression found.")
- Counts (e.g., "Updated:6, Skipped:0, Ignored:0")
- Notes (e.g., "Dependencies is not mapped... skipping")

Tips for Troubleshooting

When troubleshooting or checking a strategy's status:

Start with the status: look for any obvious errors or red flags.
Check filters and deltas: If no data is updated but no errors appear, verify whether filters or delta settings might be excluding the plan.
Compare IDs: Confirm if the item or plan ID is being grabbed and processed by the strategy.
Analyze failure patterns:
- Random/single failures may be transient and non-reproducible.
- Consistent failures for a specific item likely point to a configuration or data issue.
- All items failing usually indicate a system-wide issue, such as data error, or incorrect field mappings.

If the error message is unclear, consult our integration troubleshooting pages.

When to Open a Support Ticket

Not all errors are cause for concern. Integrations were designed to recover from errors, by processing items (plan, resource etc) that failed to update/create the next time a job runs.

Examples where errors are not cause for concern:

The source data includes a plan that cannot be found in OnePlan. Depending on the settings and the source of the data, there is a possibility that it is normal that some plans are not stored or managed in OnePlan.
Items fail to update due to an error a single time over a period of days. As the failed items will be processed again, they will "auto recover".

Examples where the data and logs should be reviewed more closely:

If the whole job fails with an error message and nothing is processed and the status of the job is "Failed". In this case, the error could be a login issue that must be solved.
The same item (plan or resource) fails to be created or updated due to errors over and over again. In this case, the item will not auto recover as there is a reason why the item cannot be updated.

Creating a Support Ticket

When submitting a Support ticket to troubleshoot an integration error, please include:

Integration URL - Found in the address bar, usually in the format of my.oneconnect.ai/Integrations/{IntegrationID}.
Strategy Name - Especially important if multiple strategies are scheduled.
Expected vs. Actual behavior - Explain what you expected to happen, and describe what actually happened. This helps our Support Team understand the issue and provide a faster, more accurate response.

Related to

Integration