Cloud Replicator Documentation
Index

Engine Status

Cloud Replicator uses parallel replication engines to process data efficiently. The Engine Pulse List provides real-time visibility into active engines.

Overview

The Engine Pulse system:

  • Tracks active replication engines
  • Updates every 10 seconds during replication
  • Shows progress and performance metrics
  • Helps identify stuck or slow engines

Accessing Engine Status

From Table Mapping

  1. Open the Table Mapping page
  2. Click See Running Engines in the action bar

From Replication Log

  1. Open the Replication Log
  2. Find an entry with "Running" status
  3. Click the Status to drill down

Direct Access

  1. Search for "Engine Pulse" in Business Central
  2. Open the Engine Pulse List page

Understanding the Engine Pulse List

Displayed Fields

Field Description
Engine ID Unique identifier for the engine session
Company Company currently being processed
Table No. Table number being replicated
Destination Target cloud service
Start Time When this engine started
Elapsed Time since engine started
Records Replicated Count of records processed
Records Deleted Count of deletions processed
Rate Records per second
Status Running, Stale, or Stopped

Status Indicators

Status Meaning
Running Engine is actively processing
Stale No update in >10 seconds
Stopped No update in >100 seconds (completed or terminated)

Interpreting Engine Data

Normal Operation

Active engines show:

  • Status = Running
  • Elapsed increasing
  • Records Replicated increasing
  • Rate showing throughput

Stale Engine

A stale engine may indicate:

  • Processing a large record
  • Waiting for cloud response
  • Potential hang or issue

If stale for extended period:

  • Check cloud destination status
  • Review network connectivity
  • May need intervention

Stopped Engine

Engine has finished:

  • Completed its assigned work
  • Encountered an error
  • Timed out

Check Replication Log for final status.

Monitoring During Replication

Real-Time View

  1. Open Engine Pulse List
  2. Click Refresh (or press F5)
  3. View updates automatically
  4. Repeat to see progress

Multiple Engines

During parallel replication:

  • Multiple rows appear
  • Each engine shows its progress
  • Different tables/companies may be processed simultaneously

Progress Tracking

Monitor these indicators:

  • Total Records Replicated across engines
  • Individual engine rates
  • Elapsed times

Engine Configuration

Engine Count

Configured in Cloud Replicator Setup:

  • Replication Engine Count: Maximum parallel engines
  • Default: 10

Impact of Engine Count

Count Effect
Lower (5) Less system load, slower total time
Default (10) Balanced performance
Higher (20+) Faster replication, more resources used

Table Splitting

When enabled:

  • Large tables are split across multiple engines
  • Each engine processes a range of records
  • "From Entry No." and "To Entry No." show the range

Troubleshooting with Engine Status

No Engines Visible

If Engine Pulse List is empty:

  • No replication is running
  • Check if Job Queue started
  • Try Manual Run to verify

Engine Stuck on Same Record Count

If Records Replicated doesn't increase:

  • Check destination availability
  • Look for error in Replication Log
  • May be processing complex records

All Engines Show Stale

Network or system issue:

  • Check Business Central session status
  • Verify cloud connectivity
  • Review system resources

Low Replication Rate

If rate is unexpectedly low:

  • Check cloud destination throttling
  • Review Retry settings
  • Consider reducing parallel engines

Engine Lifecycle

Starting Engines

When replication runs:

  1. Main engine creates replication parameters
  2. Background sessions start (up to Engine Count)
  3. Each session appears in Engine Pulse List

During Processing

Each engine:

  1. Picks up work from parameter queue
  2. Processes records
  3. Updates pulse every 10 seconds
  4. Creates Replication Log entries

Completion

When work is done:

  1. Engine marks log as Completed
  2. Pulse stops updating
  3. Session terminates
  4. Row remains until overwritten

Canceling Replication

There is no direct cancel button, but you can:

Wait for Timeout

Engines timeout based on Engine Timeout setting (default: 24 hours).

Restart Business Central

Closing the session terminates background engines. Note: This affects all activity.

Reduce Future Impact

If replication is too long:

  • Split into smaller batches
  • Reduce table mappings
  • Schedule during off-hours

Best Practices

Monitor Initial Replications

First-time replications:

  • Watch Engine Pulse closely
  • Verify engines are progressing
  • Note typical rates for reference

Compare to Baseline

Track normal performance:

  • Typical rates per table
  • Usual completion times
  • Number of engines used

Investigate Anomalies

When metrics differ from baseline:

  • Check for data volume changes
  • Review cloud service status
  • Look for concurrent activity

Engine Performance Tips

Optimal Engine Count

Find the right balance:

  • Start with default (10)
  • Increase if replication is slow and system has capacity
  • Decrease if seeing throttling or errors

Table-Specific Tuning

Some tables benefit from:

  • More engines (large tables)
  • Fewer fields (reduce payload)
  • SystemId as RowKey (simpler keys)

Peak Time Awareness

During business hours:

  • Consider fewer engines
  • Monitor user experience
  • Run large replications off-hours