topic Qlik rest api behaviour doubt in Qlik Replicate

Qlik rest api behaviour doubt

tulika — Tue, 30 Dec 2025 06:00:16 GMT

Hi team,

for automating scheduled full-load qlik replicate tasks via script, I have used qlik rest api endpoints(java implementation).

1 task can contain n tables. To reload a table, I need to call reload table api + run task api. my script allows to reload 1 table, as per user requirement. My doubt is if the task is already running to reload 1 table, how should I handle the new script command to reload other table. Should it wait for the task to stop first, before requesting reload new table.

Right now, i wrote my script like that, but for few replication tasks which have large number of tables, the other calls just keep waiting.

Thanks in advance!

Re: Qlik rest api behaviour doubt

DesmondWOO — Fri, 02 Jan 2026 08:02:40 GMT

Hi @tulika ,

Since your task is running, I believe running "ReloadTable" API should be enough.

Regards,
Desmond

Re: Qlik rest api behaviour doubt

tulika — Mon, 05 Jan 2026 06:16:37 GMT

Hello @DesmondWOO , thanks. I have tried this. But only reloadTable call is just putting the tables in queue forever.

Re: Qlik rest api behaviour doubt

DesmondWOO — Tue, 06 Jan 2026 08:49:44 GMT

Hi @tulika ,

I could not reproduce your problem. I called the REST API using POSTMAN.

https://{{hostname}}/attunityenterprisemanager/api/v1/servers/{{servername}}/tasks/Des-MSSQL-ANY/tables?action=reload&schema=dbo&table=test05

The table test05 was reloaded.

By default, Qlik Replicate loads up to five tables concurrently. Any additional tables are placed in a queue until resources become available.

If the issue persists, please open a support with us. Thanks!

Regards,
Desmond

Re: Qlik rest api behaviour doubt

tulika — Wed, 07 Jan 2026 06:27:09 GMT

hello @DesmondWOO , thank you. Could you please confirm the state of your qlik rep task before the call (was it already running or not) and your version of qlik too

Re: Qlik rest api behaviour doubt

DesmondWOO — Wed, 07 Jan 2026 07:57:56 GMT

Hi @tulika ,

Environment
Qlik Replicate: v2024.11.0.814
Qlik Enterprise Manager: v2025.5.0.411
Task Type: Full Load + Apply Changes

Steps to Reproduce

Reload the task.
Once the task enters the CDC stage, issue the RELOAD API on a table
In the Monitor view, observe that the “Loaded On” timestamp has changed.

For further investigation, I will need your diagnostic package to review the versions and settings. Because the package contains server information, it should not be uploaded to the forum. Therefore, I recommend opening a new ticket so we can proceed securely.

Regards,
Desmond

Re: Qlik rest api behaviour doubt

tulika — Wed, 07 Jan 2026 08:25:55 GMT

hello, Thanks, just to conclude from here. My task is of type full load...it runs only via api call too and not in cdc

Re: Qlik rest api behaviour doubt

DesmondWOO — Wed, 07 Jan 2026 10:21:23 GMT

Hi @tulika ,

I believe I now understand your scenario. Please see my recommendations below:

GUI Reloads: Qlik Replicate supports task scheduling. You can configure a schedule to automatically reload all tables, without writing script.
API-Based Reloads: If you need to start a task via API, you can use the RunTask API with the option RELOAD_TARGET.
API-Based Reloads Specific Tables:
1. Use the ReloadTable API to add individual tables one by one. In the Qlik Replicate console, you will see these tables queued for reload.
2. Then, run the RunTask API with the option RESUME_PROCESSING to process the queued tables.

Please let me know if this approach works for you.

Regards,
Desmond

Re: Qlik rest api behaviour doubt

tulika — Wed, 07 Jan 2026 10:26:03 GMT

Thank youu!