Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik and ServiceNow Partner to Bring Trusted Enterprise Context into AI-Powered Workflows. Learn More!
cancel
Showing results for 
Search instead for 
Did you mean: 
iti-attunity-sup
Partner - Creator III
Partner - Creator III

Specifications for the `repctl gettaskstatus` command

I had been using the following “repctl gettaskstatus” command in Qlik Replicate to check the task status.

Example: .\repctl.exe -d "C:\Program Files\Attunity\Replicate\data" connect; gettaskstatus task=<task name>

Recently, after upgrading Qlik Replicate to version 2025.11, this command began to fail.

C:\Program Files\Attunity\Replicate\bin>.\repctl.exe -d "C:\Program Files\Attunity\Replicate\data" connect; gettaskstatus task=Oracle19c_to_AzureSQL
[connect; command] Succeeded
[gettaskstatus command] Failed
command gettaskstatus: required argument monitor_data is not provided (exit status 20014)

I followed the instructions and specified the `monitor_data` argument, and it worked.

C:\Program Files\Attunity\Replicate\bin>.\repctl.exe -d "C:\Program Files\Attunity\Replicate\data" connect; gettaskstatus task=Oracle19c_to_AzureSQL monitor_data=true;
[connect; command] Succeeded
command gettaskstatus response:
{
"task_status": {
"name": "Oracle19c_to_AzureSQL",
"state": "STOPPED",

 

With that in mind, here are my questions.

Question 1
Is my understanding correct that the specifications for this command changed starting with the November 2025 version?

Question 2
Please explain the meaning of the `monitor_data` argument.

 

Best Regards

Hironori Fujihira

 

 

Labels (1)
1 Solution

Accepted Solutions
SachinB
Support
Support

Hello @iti-attunity-sup 

Yes, the monitor_data parameter appears to have been introduced in the November 2025 version of Qlik Replicate.

In this version, the repctl help command=gettaskstatus output shows:

monitor_data: required BOOL

However, in earlier versions, this parameter is not present.

 

SachinB_2-1775806825794.png

 

 

monitor_data is expected to: Include detailed monitoring information about the task Observed Behavior

Despite using different values:

monitor_data=true

C:\Program Files\Attunity\Replicate\bin>repctl -d "C:\Program Files\Attunity\Replicate\data" connect; gettaskstatus task=SAPHANA_TO_TB_Snowflake monitor_data=true


monitor_data=false

C:\Program Files\Attunity\Replicate\bin>repctl -d "C:\Program Files\Attunity\Replicate\data" connect; gettaskstatus task=SAPHANA_TO_TB_Snowflake monitor_data=false

 

Both commands are returning the same output, without any noticeable difference in monitoring details.

 

Could you please create a support case for this issue so that the R&D team can investigate further and provide clarification on this.

Thanks for understanding.


Regards,

Sachin B

View solution in original post

1 Reply
SachinB
Support
Support

Hello @iti-attunity-sup 

Yes, the monitor_data parameter appears to have been introduced in the November 2025 version of Qlik Replicate.

In this version, the repctl help command=gettaskstatus output shows:

monitor_data: required BOOL

However, in earlier versions, this parameter is not present.

 

SachinB_2-1775806825794.png

 

 

monitor_data is expected to: Include detailed monitoring information about the task Observed Behavior

Despite using different values:

monitor_data=true

C:\Program Files\Attunity\Replicate\bin>repctl -d "C:\Program Files\Attunity\Replicate\data" connect; gettaskstatus task=SAPHANA_TO_TB_Snowflake monitor_data=true


monitor_data=false

C:\Program Files\Attunity\Replicate\bin>repctl -d "C:\Program Files\Attunity\Replicate\data" connect; gettaskstatus task=SAPHANA_TO_TB_Snowflake monitor_data=false

 

Both commands are returning the same output, without any noticeable difference in monitoring details.

 

Could you please create a support case for this issue so that the R&D team can investigate further and provide clarification on this.

Thanks for understanding.


Regards,

Sachin B