Cloud Replicator Documentation
Index

Replication Log

The Replication Log provides a complete history of all replication operations. This guide explains how to use and interpret the log.

Overview

The Replication Log captures:

  • Every replication operation
  • Start and end times
  • Record counts
  • Success or failure status
  • Error messages when failures occur

Accessing the Replication Log

From Table Mapping

  1. Open the Table Mapping page
  2. Click the Replications count for a specific mapping
  3. The log opens filtered to that table

Direct Access

  1. Search for "Replication Log" in Business Central
  2. Open the Replication Log page
  3. All replication history is displayed

Log Entry Fields

Field Description
Log Timestamp when the log entry was created (Replication Time)
Table No. Business Central table number
Replication Engine ID ID of the engine that processed this job
Destination Target cloud service
Company Business Central company
Start Time When replication started
End Time When replication completed
Elapsed Duration of replication
Records Replicated Number of records processed
Records Deleted Number of deletions replicated
From Entry No. Starting primary key (for table splitting)
To Entry No. Ending primary key (for table splitting)
Status Current status (see below)
Error Message Error details if failed

Status Values

Status Meaning
Started Replication is in progress
Completed Successfully finished
Failed Error occurred
Reset Log was reset for resync

Dynamic Status Display

When viewing the log, the Status field shows real-time information:

  • Running: Active engine is processing
  • Stalled: Engine hasn't updated pulse recently
  • Otherwise shows the actual status

Using the Replication Log

Viewing Recent Activity

  1. Open Replication Log
  2. Sort by Log (descending) to see newest first
  3. Review recent entries for status

Filtering by Table

  1. Use the filter pane
  2. Filter on Table No.
  3. View history for specific table

Filtering by Status

  1. Filter on Status field
  2. Common filters:
    • Status = Failed (find errors)
    • Status = Completed (verify success)

Viewing Errors

  1. Filter for Status = Failed
  2. Review the Error Message column
  3. Look for patterns in failures

Interpreting the Log

Successful Replication

A successful entry shows:

Status: Completed
Records Replicated: 1,234
Records Deleted: 5
Elapsed: 0:02:35
Error Message: (empty)

Failed Replication

A failed entry shows:

Status: Failed
Records Replicated: 500
Elapsed: 0:01:15
Error Message: "Connection refused: Storage account..."

In-Progress Replication

While running:

Status: Started (or Running in display)
Start Time: [timestamp]
End Time: (empty)
Elapsed: (calculating)

Performance Metrics

Replication Rate

The log shows calculated rate (Records/second):

Records Replicated: 10,000
Elapsed: 0:05:00
Rate: ~33 records/second

Identifying Slow Tables

  1. Sort by Elapsed (descending)
  2. Find tables taking longest
  3. Consider:
    • Reducing fields (Field Actions)
    • Increasing engine count
    • Running during off-peak hours

Compare replication times over days/weeks:

  • Increasing times may indicate growing data
  • Sudden increases may indicate issues
  • Consistent times indicate stable operation

Drill-Down Actions

View Running Engines

From Status field showing "Running":

  1. Click the Status value
  2. Engine Pulse List opens
  3. View real-time progress

From the log entry:

  1. Note the Table No.
  2. Navigate to Table Mapping
  3. Filter to find the mapping

Log Maintenance

Log Retention

Log entries accumulate over time. Consider:

  • Periodic cleanup of old entries
  • Archiving for compliance
  • Database size monitoring

Cleaning Old Entries

Business Central standard procedures apply:

  • Use date compression if available
  • Delete old entries manually
  • Consider retention policies

Common Patterns to Watch

Intermittent Failures

Multiple failures with same error:

  • Network connectivity issues
  • Cloud service throttling
  • Credential problems

Increasing Duration

Gradual increase in elapsed time:

  • Data volume growing
  • Consider table splitting
  • Review field actions

Zero Records Replicated

Completed with 0 records:

  • May be normal (no changes)
  • Or filter too restrictive
  • Check company filter settings

Frequent Resets

Many Reset status entries:

  • Manual resets for troubleshooting
  • May indicate sync issues
  • Review underlying cause

Troubleshooting with Logs

Connection Errors

Look for patterns in Error Message:

  • "Connection refused": Network/firewall issue
  • "401 Unauthorized": Invalid credentials
  • "429 Too Many Requests": Throttling

Data Errors

Errors during record processing:

  • "Invalid value": Data type mismatch
  • "Key too long": Primary key exceeds limits
  • "Duplicate key": Conflict in destination

Timeout Errors

If replication times out:

  • Increase Engine Timeout in Setup
  • Reduce records per engine
  • Check for blocking operations

Best Practices

Regular Review

Check the log regularly:

  • Daily for active replications
  • After Job Queue runs
  • When issues are reported

Document Investigations

When troubleshooting:

  • Note the Log timestamp
  • Record the error message
  • Document resolution

Alert on Failures

Consider setting up notifications:

  • Monitor Job Queue for failures
  • Create workflows on error patterns
  • Proactive monitoring