Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
What all activities happens in background when reload is triggered through Qliksense scheduler? looking for step wise detailed explanation.
Someone else can probably provide definitive information, but this is what I have observed for our tasks. For a successful task, the execution results are:
Changing task state to Triggered.
Trying to start task. Sending task to slave scheduler
Changing task state from Triggered to Started
Reference to scriptlog added
Changing task state from Started to FinishedSuccess
The possible execution statuses are below:
0,"Never Started"
1,"Triggered"
2,"Started"
3,"Queued"
4,"Abort Initiated"
5,"Aborting"
6,"Aborted"
7,"Finished Success"
8,"Finished Failed"
9,"Skipped"
10,"Retry"
11,"Error"
12,"Reset"
At a first approximation based on knowledge and a few hunches:
I'll chime in here from the Scheduler perspective:
On top of this there is various levels of timeouts, internal details of the Engine, and various entities the Master scheduler creates, updates, and removes from the Repository (ExecutionSession, ExecutionResult, ...).
Besides this basic flow there are also other states which will be entered
Hi Turner,
You mentioned the below point from the list.
What is "Saves the Diff" in the sentence. Could you please explain. what will save in Transactions folder.
Regards
Srinivas