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

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Announcements
Posting on Qlik Community is temporarily paused for some users. Thank you for patience and we'll update you soon!
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
tynernies
Contributor
Contributor
a week ago

Clarification needed: /api/v1/reload-tasks deprecation and identifying affected integrations

We received a notice that an external integration or Qlik Automate modified a reload task through /api/v1/reload-tasks and should move to /api/scheduling/tasks before November 26, 2026.

The deprecation changelog says that creating tasks through the old API stops on November 26, while updates and deletes of existing tasks remain possible until each task is migrated. Could Qlik clarify:

  1. Will all old API write calls fail on November 26, or only task creation? Can updates to an unmigrated task continue after that date?
  2. How can a tenant administrator identify the specific integration, API key, or Automate workflow that made the old API call? Our task audit events show changes but do not include the HTTP method or request path.
  3. Does this change affect POST /api/v1/reloads, which triggers an immediate app reload, or only the reload-task management API?

We want to identify the actual caller and migrate it without disrupting scheduled or on-demand reloads. Thanks for any guidance.

Labels (2)
Labels
6 users say endorse
264 Views
1 Reply
Dave_Channon
Employee
Employee
yesterday

Please open a support case and request additional information there - we have some limited additional insights which will help you identify the user. All POST/PATCH/DELETE calls will fail from that date as we'll be migrating those events to the new tasks service in the background.

For Qlik Automate, it is possible to scan all workflows in your org using the Qlik platform operations connector and an OAuth client with the automate admin scope (https://qlik.dev/changelog/241-admin-automations-scope-update/). This will allow you to scan the JSON for either reload task blocks, or /v1/reload-tasks text.

11 Views