Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
fmcrashid
Contributor II
Contributor II

how to exit/abort task with out update?

Hi All

We need the ability to "Abort" the current qlikview load with the following consequences:

1 - Do not save the file (leave the old file intact)

2 - Do not trigger the dependent workflows in the QMC

3 - Do not distribute the bad file

In our current process, by “failing” the workflow using a bad command, ALL THREE of these requirements are met but large number of intentional failures affect system performance.

Any solutions? suggestions? similar situation you were in and how did you resolve/workaround it?

Thanks and reply will be much appreciated.

Labels (4)
1 Solution

Accepted Solutions
Miguel_Angel_Baeyens

In the QMC, when a task fails the reload, the file is not distributed and the QMC will show "Failed" in the task status, and any depending tasks, if configured properly (e.g.: trigger > in the event of a successful reload of the previous task) will not run, since the condition is false (the task was not successfully reloaded). Likewise, if while a task is running the "Stop" button is clicked, the task will stop and fail if it's running the script, if the script was already executed and the file in the process of being distributed, the distribution may fail, but the original app will be saved as it didn't fail.
Moreover, QlikView Distribution Service uses a Source Document folder (the one that is reloaded and distributed) and a User Document folder (the one that stores the resulting distributed apps).

I'm missing on the "large number of intentional failures": aborting tasks in the QMC is slowing down the environment?

View solution in original post

1 Reply
Miguel_Angel_Baeyens

In the QMC, when a task fails the reload, the file is not distributed and the QMC will show "Failed" in the task status, and any depending tasks, if configured properly (e.g.: trigger > in the event of a successful reload of the previous task) will not run, since the condition is false (the task was not successfully reloaded). Likewise, if while a task is running the "Stop" button is clicked, the task will stop and fail if it's running the script, if the script was already executed and the file in the process of being distributed, the distribution may fail, but the original app will be saved as it didn't fail.
Moreover, QlikView Distribution Service uses a Source Document folder (the one that is reloaded and distributed) and a User Document folder (the one that stores the resulting distributed apps).

I'm missing on the "large number of intentional failures": aborting tasks in the QMC is slowing down the environment?