Event not completing wait for event task

[#1]

Hi,

In 4.6C we have a wait for event step in a workflow. This worked so far w/o any problems, but we just came accross two instances where SWEL shows that the event was raised for the object instance, but the status says "No receiver entered" as if there was no workflow waiting for the event.

This is quite strange, since the wait step was started 5 days before the event was raised, and the instance linkage in the step shows the particular object instance and the event it is waiting for.

Any ideas what might cause this?

Thanks,

KK

[Former Member · Accepted solution]

Hi,

I assume the keys are identical?

Check SWEQADM if there are any events not correct.

Kind regards, Rob Dielemans

[Former Member · Accepted solution]

Yep, keys are the same...

SWEQADM shows nothing, event queue is not active.

[Former Member]

Hi All,

Thanks for the replies, problem was the deactivated event linkage.

Killer was that it deactivated only for a short period, then it was activated again, so when I was looking for the problem, it already showed activated. Fortunately SWETYPEENA is logged, so I found the entries in DBTABLOG for the deactivation and activation.

Just for info, the deactivation happened because two different wait for event steps received their terminating event. After the first was received, workflow started to logically delete the parallel steps on the fork branch, and it was still locking the workitems when the second event was raised. Hence second event could not start the receiver and deactivated the instance linkage according to system default setting.

Now we will probably change this event linkage not to deactivate when problem occurs, since we have many workflows with parallel wait for event steps.

Regards,

KK

[Former Member]

Hello,

Thanks for the follow-up with the detailed explanation. If only everyone did that!

"it deactivated only for a short period, then it was activated again"

How did it get activated again?

regards

Rick Bakker

hanabi technology

[Former Member]

Hi Rick,

DBTABLOG shows that the linkage was activated by a user. At that time the user was processing one of these workflows, and right at the DBTABLOG linkage activation time was the wait for event step started which was linked to this event. So the system activated the event linkage right away when the next wait for event with this linkage type was created.

Unfortunately between the deactivation and activation time there were a few events raised which did not get to the workflows.

Regards,

Krisztian Klausz

[raviahuja]

Hi,

Check in T-code SWE2 if linkage (Type Linkage checkbox should be ticked) between Event and Receiver Type for Your event and WF. If it is not ticked, then you would have to delete and create a new linkage. The tick normally is removed when WF goes in error sometimes.

When you create new linkage, make sure you select 'Do not change linkage' in field 'Behavior Upon Error Feedback'. this will preven linkage to be removed even when WFs goes into error.

Thanks.

Ravi

[sudhahar_ramachandran]

Make sure your workflow is not deactivated because of some error (usually the reason will be like 'mandatory field is not passed'). check when is the last time this event had a receiver. check any event linkage is deactivated after that.

hope this helps.

with regards,

Sudhahar R.