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

Announcements
Now accepting applications for the Qlik Luminary and Partner Ambassador Programs: Apply by July 6!
cancel
Showing results for 
Search instead for 
Did you mean: 
Paulo_IntelFab
Contributor III
Contributor III

Schedule failing to start in Qlik Cloud

Hi, there. 

From today around 4AM the scheduling service for my tenant stop working in all kind of tasks (loads, reports and subscriptions), as can be seen in the image. 

How can: 
- Understand the cause of this problem?
- Restart the scheduling so they work normally?
- Avoid this problem happen again?

Labels (1)
  • SaaS

1 Solution

Accepted Solutions
Greg_Taffer
Support
Support

Based on the behavior described, the Qlik Cloud scheduling service has likely encountered a backend error, a capacity limit, or a task dependency failure that stopped the scheduling engine. In Qlik Cloud (SaaS), you cannot restart services directly like on-premise, but you can resolve this through task management and monitoring. 
 

1. Understand the Cause of the Problem
 

  • Check Qlik Cloud Status: The first step is to check if there is an incident affecting your tenant region. Go to status.qlikcloud.com to review any ongoing incidents or maintenance that began around 4 AM.
  • Review Task Details (Reload History):
    • Navigate to the Analytics activity center > Tasks (or app details > reload history).
    • Click the three ellipses > Details > Reload History on a failed task to see the error message.
  • Check for 5 Consecutive Failures: Tasks set to reload automatically can be deactivated if they fail 5 consecutive times. Check if your tasks have been automatically set to inactive.
  • Check for Task Dependency Failures: If your tasks are chained (e.g., Task B starts after Task A succeeds), a failure in the initial task will stop all downstream scheduling. 

2. Restart/Restore Scheduling
 

  • Run Tasks Manually: In the Tasks section, select a task and click Run now to test if the engine is responding.
  • Re-activate Tasks: If tasks were deactivated due to consecutive failures, you will need to manually re-activate them.
  • Check for "Stuck" Tasks: If tasks are stuck in a "Triggered" state, you may need to use the task menu to stop them and then restart them.
  • Remove & Recreate Tasks: If a specific task is corrupted, deleting it and recreating it can sometimes resolve the issue. 

3. Avoid This Problem in the Future
 

  • Set Up Notifications: Configure alert notifications to be sent when tasks fail, allowing you to address issues before they cause 5 failures and deactivate.
  • Review Scheduled Times: If tasks fail due to capacity limits at 4 AM, consider staggering your reloads to reduce the load on the scheduling engine at a single peak time.
  • Monitor Task Ownership: If tasks were created by a user who has left the organization or had their access revoked, the tasks will fail. Ensure tasks are owned by a service account or an active admin.
  • Utilize Qlik Cloud APIs: For more advanced monitoring, set up a Task Monitor application using Qlik Cloud APIs to keep track of failures in real-time.

View solution in original post

3 Replies
Greg_Taffer
Support
Support

Based on the behavior described, the Qlik Cloud scheduling service has likely encountered a backend error, a capacity limit, or a task dependency failure that stopped the scheduling engine. In Qlik Cloud (SaaS), you cannot restart services directly like on-premise, but you can resolve this through task management and monitoring. 
 

1. Understand the Cause of the Problem
 

  • Check Qlik Cloud Status: The first step is to check if there is an incident affecting your tenant region. Go to status.qlikcloud.com to review any ongoing incidents or maintenance that began around 4 AM.
  • Review Task Details (Reload History):
    • Navigate to the Analytics activity center > Tasks (or app details > reload history).
    • Click the three ellipses > Details > Reload History on a failed task to see the error message.
  • Check for 5 Consecutive Failures: Tasks set to reload automatically can be deactivated if they fail 5 consecutive times. Check if your tasks have been automatically set to inactive.
  • Check for Task Dependency Failures: If your tasks are chained (e.g., Task B starts after Task A succeeds), a failure in the initial task will stop all downstream scheduling. 

2. Restart/Restore Scheduling
 

  • Run Tasks Manually: In the Tasks section, select a task and click Run now to test if the engine is responding.
  • Re-activate Tasks: If tasks were deactivated due to consecutive failures, you will need to manually re-activate them.
  • Check for "Stuck" Tasks: If tasks are stuck in a "Triggered" state, you may need to use the task menu to stop them and then restart them.
  • Remove & Recreate Tasks: If a specific task is corrupted, deleting it and recreating it can sometimes resolve the issue. 

3. Avoid This Problem in the Future
 

  • Set Up Notifications: Configure alert notifications to be sent when tasks fail, allowing you to address issues before they cause 5 failures and deactivate.
  • Review Scheduled Times: If tasks fail due to capacity limits at 4 AM, consider staggering your reloads to reduce the load on the scheduling engine at a single peak time.
  • Monitor Task Ownership: If tasks were created by a user who has left the organization or had their access revoked, the tasks will fail. Ensure tasks are owned by a service account or an active admin.
  • Utilize Qlik Cloud APIs: For more advanced monitoring, set up a Task Monitor application using Qlik Cloud APIs to keep track of failures in real-time.
marksouzacosta
MVP
MVP

FYI We found the same problem in the same day and time.

marksouzacosta_0-1775187884699.png

 

Regards,

Mark Costa

 

Read more at Data Voyagers - datavoyagers.net
Follow me on my LinkedIn | Know IPC Global at ipc-global.com

Paulo_IntelFab
Contributor III
Contributor III
Author

I've run through the steps to recover the scheduling of all tasks (run manually and deactivate/activate the schedulled tasks). And it worked well.