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:
Will all old API write calls fail on November 26, or only task creation? Can updates to an unmigrated task continue after that date?
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.
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.
