nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Tasks mentioned in iwevents.log

nirali

I see following entries in iwevents.log all the time. but dont ub=nderstand them.

1) ChooseTransition - Its an activity that a user is doing. What does this mean ?

2) TaskActivate and TaskGoActive - I see all the time TaskActivate, TaskInactivate and TaskGoActive with every user logon. Whats the difference between these tasks.

3) I see deployment log file in OD and want to find out whi started this deployment. So I ckeck the time stamp and look for the same time stamp in iwevents.log file. But all the time on this time stamp, the user I see is master(which is SYSTEM) and when I go little above then I see the user name. So I guess user initiates the wf and when it reaches the deployment task, SYSTEM triggers this deployment. Only thing is there is 10 seconds gap between the user starting the job and external task being triggered. Does it take this long for wf to reach deployment task?

Pls explain.

Find more posts tagged with

Comments

Adam Stoller

I see following entries in iwevents.log all the time. but dont ub=nderstand them.

1) ChooseTransition - Its an activity that a user is doing. What does this mean ?

2) TaskActivate and TaskGoActive - I see all the time TaskActivate, TaskInactivate and TaskGoActive with every user logon. Whats the difference between these tasks.

3) I see deployment log file in OD and want to find out whi started this deployment. So I ckeck the time stamp and look for the same time stamp in iwevents.log file. But all the time on this time stamp, the user I see is master(which is SYSTEM) and when I go little above then I see the user name. So I guess user initiates the wf and when it reaches the deployment task, SYSTEM triggers this deployment. Only thing is there is 10 seconds gap between the user starting the job and external task being triggered. Does it take this long for wf to reach deployment task?

Pls explain.

The information in the iwevents.log are just that - events. Someone chooses a transition from amongst those offered to them (e.g.: "Approve", "Reject", etc.) and you can see which one they chose by looking further along the line. When they choose a transition, one task (the current one) becomes inactive, and another one (the one being transitioned to) becomes active.
With regard to your last question - Windows doesn't provide for true (or at least simple) impersonation, so the automated tasks tends to be performed by SYSTEM, whereas the user-oriented tasks are performed by the logged-in user. How long it takes to get from the initial invocation of the job until the deployment occurs is completely dependent upon what actually happens between those two events - and thus is distinctly site / implementation dependent.

khyati

Thanks. That helps.

When a user chooses an option task related to that option becomes active and when that task completes it becomes inactive and the next task becomes active, right ?

Can you pls explain whats the difference between TaskActivate and TaskGoActive ?

thanks

Adam Stoller

Thanks. That helps.

When a user chooses an option task related to that option becomes active and when that task completes it becomes inactive and the next task becomes active, right ?

Can you pls explain whats the difference between TaskActivate and TaskGoActive ?

thanks

The log probably looks something like this:

[date] userid role ChooseTransition wf-name wfid EmailTask58   0xd03 0 Flow59 3          areavpath
[date] userid role TaskActivate     wf-name wfid ExternalTask2 0xd01   EmailTask58 0xd03 areavpath
[date] userid role TaskInactivate   wf-name wfid EmailTask58   0xd03                     areavpath
[date] userid role TaskGoActive     wf-name wfid ExternalTask2 0xd01                     areavpath

I'm not positive about all the parts, but I read it as follows:

accurate interpretation.In looking at this - I believe my earlier statement about ChooseTransition being related to a user selecting a possible transition was over simplified - I believe it relates to any time a callback is performed - regardless of whether it is automated via a script or manually selected via a user.

nirali

What you explained that looks very simple. But when I look at log files, its confusing. I will put a code from my log file.

[Thu Oct 09 21:13:05 2008] aim\ravi.kumar editor Submit areavpath 0x00004150000000002bg1kn5
[Thu Oct 09 21:13:05 2008] SYSTEM master TaskActivate publish_content 0xbmmek deploy_content 0xbmmej submit_to_staging 0xbmmei areavpath
[Thu Oct 09 21:13:05 2008] SYSTEM master TaskInactivate publish_content 0xbmmek submit_to_staging 0xbmmej
areavpath
[Thu Oct 09 21:13:05 2008] SYSTEM master TaskGoActive publish_content 0xbmmek deploy_content 0xbmmej
areavpath
[Thu Oct 09 21:13:05 2008] SYSTEM master TaskInvokeExternal publish_content 0xbmmek deploy_content 0xbmmej
areavpath
[Thu Oct 09 21:13:08 2008] SYSTEM master TaskCalledBack publish_content 0xbmmek deploy_content 0xbmmej 0 3 areavpath
[Thu Oct 09 21:13:08 2008] SYSTEM master ChooseTransition publish_content 0xbmmek deploy_content 0xbmmej 0 3 areavpath

1) In this code Ravi kumar has logged in as editor and did submit activity in the workarea specified by areavpath. whats the long number for ?

2) System has acknowledged the receipt of task by TaskActivate. Is publish_content wfid is a workflow. deploy_content taskid is a task and submit_to_staging taskid is a task , right ? Does it mean that deploy_content and submit to staging tasks in the wf are activated publish_content at the same time ? If yes, why is deploy_content task acticated at this time ?

3) System has deactivated submit task of the publish_content wf and acknowledgement is TaskInactivate. (why is the wf name there ?) Is submit to staging task deactivated ?

4) System activates deploy_content task of publish_content wf to deploy content from specified areavpath. Over here actual deployment starts, right ?Is this an external task ? If not, then what different thing does this task do than external task. As actual deployment is done by external task only, right ?

5) System invokes external task to deploy content to specified areavpath. Is this task and deploy_content task are different ?

6) whats this taskcalledback for ?

Pls explain. If some of the questions are particular environment specific, pls reply about what can it be for as per your experience. I am asking this question in bits and pieces now.

thanks.

Adam Stoller

This is a somewhat interesting thread, as I don't know that we've ever discussed workflow events in such detail before, and I don't think it is all that well documented in any of the manuals (see page 223 of the TeamSite Administration Guide - Release 6.7.1 Service Pack 1 - Windows)


[1]aim\ravi.kumar editor Submit areavpath 0x00004150000000002bg1kn5
[2]SYSTEM         master TaskActivate       publish_content 0xbmmek deploy_content    0xbmmej submit_to_staging 0xbmmei areavpath
[3]SYSTEM         master TaskInactivate     publish_content 0xbmmek submit_to_staging 0xbmmej                           areavpath
[4]SYSTEM         master TaskGoActive       publish_content 0xbmmek deploy_content    0xbmmej                           areavpath
[5]SYSTEM         master TaskInvokeExternal publish_content 0xbmmek deploy_content    0xbmmej                           areavpath
[6]SYSTEM         master TaskCalledBack     publish_content 0xbmmek deploy_content    0xbmmej 0  3                      areavpath
[7]SYSTEM         master ChooseTransition   publish_content 0xbmmek deploy_content    0xbmmej 0  3                      areavpath

There are some strange things in the above excerpt:

nirali

Values of taskID and jobID are not real, but similar to real.
This is from wft workflow
TeamSite6.7.1 SP1.

1 How do you figure out that first task is submit_to_staging ? (Logically it is. In the log files , is there any order by which I can figure out which task is first or is there any number in taskID which suggest which task is first ? I noticed, in the taskID, only last digit is changing for different tasks. Is that the right way to check which task is first ? If yes, then still theer is confusion. Some tasks dont have digit or letter in sequence e.g. submit_to_staging has task ID as 0xbmmei, deploy_content has task ID as 0xbmmej. In this case we can say submit_to_staging is a task prior to deploy_content. Now the next task externalTask has taskID as 0xbmme6. So how to relate this task with other tasks. I can say with workflow Id, I can judge this task belongs to this particular wf. But how to figure out its priority with such taskID ?
Whenever TaskActive entry is there, it will just say taskID 1 activates taskID 2. It wont mention the tasks which are not immediately activated by taskID 1
right ? Eventhough taskID 3 will be activated by taskID 2, it will be shown in log entry only when taskID 2 activates this taskID 3 and not when taskID 1 activates taskID 2.
Can one task activate 2 tasks ? OR can two tasks activate one task ?

2 In TaskActivate there are two tasks. So the taskID with lower digit number or letter is the task which activates other task, right ? In all the log entries, workflow name and jobId are there. Does it mean that all these tasks belong to that particular wf. So in that way, all the log entries pertaining to a workflow will always have wf ID mentioned, right ?

3 In TaskInactivate, there will be one task only right or can there be more than one task ? In any case if there is one task or more all those tasks are being deactivated, right ?

4 What happens when the CallBack is invoked ?

Thanks

ISCBorisB

Values of taskID and jobID are not real, but similar to real.
This is from wft workflow
TeamSite6.7.1 SP1.

1 How do you figure out that first task is submit_to_staging ? (Logically it is. In the log files , is there any order by which I can figure out which task is first or is there any number in taskID which suggest which task is first ? I noticed, in the taskID, only last digit is changing for different tasks. Is that the right way to check which task is first ? If yes, then still theer is confusion. Some tasks dont have digit or letter in sequence e.g. submit_to_staging has task ID as 0xbmmei, deploy_content has task ID as 0xbmmej. In this case we can say submit_to_staging is a task prior to deploy_content. Now the next task externalTask has taskID as 0xbmme6. So how to relate this task with other tasks. I can say with workflow Id, I can judge this task belongs to this particular wf. But how to figure out its priority with such taskID ?
Whenever TaskActive entry is there, it will just say taskID 1 activates taskID 2. It wont mention the tasks which are not immediately activated by taskID 1
right ? Eventhough taskID 3 will be activated by taskID 2, it will be shown in log entry only when taskID 2 activates this taskID 3 and not when taskID 1 activates taskID 2.
Can one task activate 2 tasks ? OR can two tasks activate one task ?

2 In TaskActivate there are two tasks. So the taskID with lower digit number or letter is the task which activates other task, right ? In all the log entries, workflow name and jobId are there. Does it mean that all these tasks belong to that particular wf. So in that way, all the log entries pertaining to a workflow will always have wf ID mentioned, right ?

3 In TaskInactivate, there will be one task only right or can there be more than one task ? In any case if there is one task or more all those tasks are being deactivated, right ?

4 What happens when the CallBack is invoked ?

Thanks

Are all these questions just educational? What is the problem you are trying to solve?

Yes, one task can activate any number of concurrent (parallel) tasks. Conversely, any number of concurrent
tasks can *merge* (in a flow sense) into single task by activating it on any number of conditions (and/or, etc...).
You can also spawn nested Workflows with the wftask Tag or from your own external/cgi/url tasks. You may
(with parallel tasks often should) activate/deactivate multiple Tasks explicitly on certain conditions, etc...What of it?

Unless you are planning some heavy WF Events *iwat* triggering I would leave all this Event details to
WF Engine. It is nice to understand them for troubleshooting and the like, when you can follow the single
WF under laboratory's conditions. Do not think for a moment though that the log may be trivial to parse in
real life, where multiple WFs of the various types are running and logging simultaneously

nirali

There is some problem with the performance of TS. I am trying to look for the activities on the TS by the user in iwevents.log. I am confused with the way log entries are displayed. Thats why I am trying to figure out how to read these entries.

Still my one question is not answered. When a wf is triggered and there are 3 tasks mentioned in one event , how to determine which task is first ? By the ascending order of number of the taskID ?

Thanks