Home / Repstance User Guide / PROCESS CONTROL COMMANDS / Status of any Capture or Apply Processes

Status of any Capture or Apply Processes

The status command shows the state of the Capture Processes and the Apply Processes and what they have done since they were started: the position of the last change in the Source Database and of the last change the process has handled, the lag, the speed and the counters. Without parameters it shows all the configured processes, whether they are running or not. The parameters process and id and the HTTP codes are explained on PROCESS CONTROL COMMANDS.

Command line (repcli)

repcli status [process=capture|apply [id=processID]]

Parameter	Description
process	capture for the Capture Processes, apply for the Apply Processes. Without it all the processes are shown.
id	The identifier of the process. It needs process. Without it all the processes of that kind are shown.

The status of all the processes. Each process has a header and the lines below it:

repcli status
Capture Process 1, Name: demo_cap, DB: AdventureWorksDW2019, Server: db-src.example.com
  RUN (In Process), Waiting for Transactions
    Last Source DB Change   :  2026/10/20 15:14:00.307 UTC (0x0000008D0000798E0007)
    Last Captured DB Change :  2026/10/20 15:14:00.307 UTC (0x0000008D0000798E0007)
  Total since  2026/10/20 04:01:00.170 UTC (0x0000008D0000778D0007):
    Processing the Transactions :  00:00:00.122
    Waiting for Transactions    :  00:16:53.921
    Average Speed (ops)         :  310.434
    Transactions   : 19 (DDL: 0,  Delete: 19,  Insert: 19,  Update: 0)

Apply Process 1, Transactions Provider (Capture): demo_cap, DB: APPLYDB, Server: db-tgt.example.com
  RUN (In Process), Waiting for Transactions
    Last Source DB Change   :  2026/10/20 15:14:00.307 UTC (0x0000008D0000798E0007)
    Last Applied DB Change  :  2026/10/20 15:14:00.307 UTC (0x0000008D0000798E0007)
    Lag                     :  00:00:00.000
  Total since  2026/10/20 04:01:00.170 UTC (0x0000008D0000778D0007):
    Processing the Transactions :  00:00:00.060
    Waiting for Transactions    :  00:11:54.103
    Average Speed (ops)         :  627.048
    Transactions   : 19 (DDL: 0,  Delete: 19,  Insert: 19,  Update: 0)

The status of the Apply Processes, here a stopped one:

repcli status process=apply
Apply Process 1, Transactions Provider (Capture): demo_cap, DB: APPLYDB, Server: db-tgt.example.com
  RUN (Completed), Waiting for the Next Command
    Last Source DB Change   :  2026/10/20 15:14:00.307 UTC (0x0000008D0000798E0007)
    Last Applied DB Change  :  2026/10/20 15:14:00.307 UTC (0x0000008D0000798E0007)
    Lag                     :  00:00:00.000
  Total since  2026/10/20 04:01:00.170 UTC (0x0000008D0000778D0007):
    Processing the Transactions :  00:00:00.060
    Waiting for Transactions    :  00:12:08.426
    Average Speed (ops)         :  627.048
    Transactions   : 19 (DDL: 0,  Delete: 19,  Insert: 19,  Update: 0)

A process that has failed shows the error after the state. Here the databases could not be reached:

repcli status
Capture Process 1, Name: demo_cap, DB: AdventureWorksDW2019, Server: db-src.example.com
  RUN (Failed), Waiting for the Next Command, [unable to open tcp connection with host 'db-src.example.com:1433': dial tcp 10.0.0.5:1433: i/o timeout]

Apply Process 1, Transactions Provider (Capture): demo_cap, DB: APPLYDB, Server: db-tgt.example.com
  RUN (Failed), Waiting for the Next Command, unable to open tcp connection with host 'db-tgt.example.com:1433': dial tcp 10.0.0.5:1433: connect: no route to host
    Last Applied DB Change  :  2026/10/20 04:01:00.170 UTC (0x0000008D0000778D0007)

How to read the output, line by line:

Line	Meaning
Capture Process 1, Name: … or Apply Process 1, Transactions Provider (Capture): …	The kind and the identifier of the process, the name of the Capture Process (for an Apply Process the Capture Process it reads from), the database and the server. For an Oracle database the connection is shown instead.
RUN (In Process), Waiting for Transactions	The last command, its status in brackets and what the process is doing. A message follows after a comma, for a failed process it is the error.
Last Source DB Change	The last change in the Source Database that the Capture Process knows. It is valid only while the Capture Process is running.
Last Captured DB Change or Last Applied DB Change	The last transaction that the process has processed successfully.
Lag (Apply Process)	The time between the last change in the Source Database and the last change that the Apply Process has applied. It is valid only while the Capture Process is running.
Total since	The time and the position of the first transaction that the process has processed since it was started. The lines below count from there.
Processing the Transactions, Waiting for Transactions, Loading the Data	How long the process has worked, waited for data and loaded data (Initial Load). Loading is shown only if the process has loaded data.
Average Speed (ops), Average Load Speed (ops)	The operations per second: inserts, updates, deletes and DDL statements divided by the processing time; the rows loaded divided by the loading time.
Transactions	The number of the transactions, and of the DDL statements, deletes, inserts and updates in them.
Loaded Objects	The tables and the rows loaded by the Initial Load. It is shown only if the process has loaded data.

The state of a process

The state is made of three values: the last command, its status and what the process is doing. The usual combinations:

State	Meaning
RUN (In Process), Waiting for Transactions	The process is running and there is nothing to process at the moment.
RUN (In Process), Processing the Transactions	The process is running and is working.
RUN (In Process), Loading the Data	The process is running the Initial Load.
RUN (Failed) with a message	The process has failed and the message is the error. The process is run again by Repstance if the attempts of the automatic restart are not used up (see Stop/Run Replication Processes).
STOP (In Process)	The process is stopping.
RUN (Completed), Waiting for the Next Command	The process has stopped: its run has completed. The Web UI shows it as Stopped.
STOP (Completed), Waiting for the Next Command	A process that had failed has been stopped.
RESET (Completed), Waiting for the Next Command	The position of the process has been reset (see Reset Process). The process is stopped. The Web UI shows it as Stopped.
RESET (Failed), Waiting for the Next Command with a message	The reset has failed, for example because the LSN is not in the trail files. The message tells why.
INITIALISED (Completed)	The process exists and no command has been executed yet.

REST API

Endpoint: https://repstance_url/control/process
Method: POST
Header: Content-Type: application/json and X-Token: token

The body of the request. The element parameters is optional: without it the status of all the processes is returned.

{
  "command": "status",
  "parameters": [
    ["process", "capture"],
    ["id", "1"]
  ]
}

The body of the answer is an array with an element for every process, or null if there is no process. The names of the fields are written exactly as below. The example shows the first element, formatted for reading:

{
  "ID": 1,
  "Process": "capture",
  "Parameter": {
    "Name": "demo_cap",
    "Server": "db-src.example.com",
    "Port": 1433,
    "Database": "AdventureWorksDW2019",
    "ConnectionType": "",
    "ServiceName": "",
    "TNSName": "",
    "DBType": "mssql"
  },
  "Command": "RUN",
  "CommandStatus": "In Process",
  "StatusDetails": "Waiting for Transactions",
  "CommandStartTime": "0001-01-01T00:00:00Z",
  "Message": "",
  "LastActivityTime": "2026-10-20T15:14:30.836566575Z",
  "StartLSN": "0x0000008D0000778D0007",
  "StartLSNTime": "2026-10-20T04:01:00.17Z",
  "CheckpointLSN": "0x0000008D0000798E0007",
  "CheckpointLSNTime": "2026-10-20T15:14:00.307Z",
  "LastDBLSN": "0x0000008D0000798E0007",
  "LastDBLSNTime": "2026-10-20T15:14:00.307Z",
  "CNTD": 19,
  "CNTI": 19,
  "CNTU": 0,
  "CNTDDL": 0,
  "CNTTX": 19,
  "CNTLOBJ": 0,
  "CNTLOBJREC": 0,
  "WAITING": 998430964468,
  "PROCESSING": 122409184,
  "LOADING": 0
}

HTTP code	Meaning
200	The request is valid. The body has the status of the processes.
401	The token is invalid.
422	The request is invalid: the JSON, the command, a parameter, or the process does not exist.

The fields of an element:

Field	Shown by repcli	Meaning
ID, Process	“Capture Process 1”	The identifier of the process and its kind, capture or apply.
Parameter	The first line	The connection of the process: Name (Capture Process) or CaptureName (the Capture Process an Apply Process reads from), Server, Port (a number), Database, DBType (mssql, oracle, postgresql, mysql, snowflake, redshift or s3) and, for Oracle, ConnectionType (ezconnect or tns), ServiceName and TNSName.
Command	The first word of the second line	The last command: INITIALISED (the process exists, no command has been executed), RUN, STOP or RESET.
CommandStatus	In brackets	Completed, In Process or Failed.
StatusDetails	After the status	What the process is doing: Waiting for the Next Command (stopped), Processing the Transactions, Waiting for Transactions or Loading the Data.
Message	After a comma	The details of the command; for a failed process the error.
CommandStartTime	Only in the JSON	Not used by this version: the value is always 0001-01-01T00:00:00Z.
LastActivityTime	Only in the JSON	The time in UTC when the activity of the process changed.
LastDBLSN, LastDBLSNTime	“Last Source DB Change”	The LSN and the time (UTC) of the last known transaction in the Source Database. The Capture Process provides them and they are valid only while it is running.
CheckpointLSN, CheckpointLSNTime	“Last Captured DB Change”, “Last Applied DB Change”	The LSN and the time (UTC) of the last transaction that the process has processed successfully.
StartLSN, StartLSNTime	“Total since”	The LSN and the time (UTC) of the first transaction processed since the process was started.
WAITING	“Waiting for Transactions”	The time in nanoseconds that the process has waited for data. repcli shows it as HH:MM:SS.FFF.
PROCESSING	“Processing the Transactions”	The time in nanoseconds that the process has processed data.
LOADING	“Loading the Data”	The time in nanoseconds that the process has loaded data (Initial Load).
CNTTX	“Transactions”	The number of the transactions.
CNTI, CNTU, CNTD, CNTDDL	“Insert”, “Update”, “Delete”, “DDL”	The numbers of the inserts, updates, deletes and DDL statements.
CNTLOBJ, CNTLOBJREC	“Loaded Objects”, “Rows”	The numbers of the objects and the records loaded by the Initial Load.

The average speed and the lag are not in the JSON. repcli calculates them: the speed is CNTI + CNTU + CNTD + CNTDDL divided by PROCESSING, the load speed is CNTLOBJREC divided by LOADING, the lag of an Apply Process is LastDBLSNTime minus CheckpointLSNTime.

Web UI

The dashboard shows every process on a card with its state (Running, Stopped or Failed), the lag, the counters and the last changes. Click “More” on the card to see the details of the process:

The window uses the same names as repcli: the state and what the process is doing, “Lag”, “Last Source DB Change”, “Last Captured DB Change” (“Last Applied DB Change” for an Apply Process), “Total since”, the time spent processing and waiting, “Average Speed (ops)” and “Transactions”. A process that has stopped, or has been reset, is shown as Stopped, and a failed process is shown as Failed with its error message. Below the state, “Details” shows the report of the transactions of the process (see Report Process). Click “Refresh” to read the status again, or tick “Auto refresh”.

Web UI, Capture process status: state, lag, speeds, transaction totals and replication report

The cards and the window are described in Monitoring Replication, the buttons of the window in Stop/Run Replication Processes and Reset Process.

Stop any Capture or Apply Processes

Reset Process