Andreas Arrgard - 2006-04-11

Logged In: YES
user_id=815211

This will solve the issue when we have marked an event
with execution-policy=always and have another event in
another step that triggers on the same message. If the
other step depends on the first one we should execute the
event with execution-policy=always first.