<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Answers to: Ivy WorkflowSystemEvent was not fired when session timeout?</title><link>https://answers.axonivy.com/questions/3776/ivy-workflowsystemevent-was-not-fired-when-session-timeout</link><description>&lt;p&gt;Hi IvyTeam,&lt;/p&gt;
&lt;p&gt;We are working on project that listen on WorkflowSystemEvent to know when the Ivy Task was created/changed. Everything working fine if we are actively change the Ivy Task, but when the user are opening the task and then his session timeout, Ivy is able to reset the Task state to SUSPENDED, but it doesn't fire the WorkflowSystemEvent, cause our application don't know the Ivy Task had changed its state to SUSPENDED.&lt;/p&gt;
&lt;p&gt;We are working on Axon.ivy 7.0.8&lt;/p&gt;</description><atom:link href="https://answers.axonivy.com/questions/3776/ivy-workflowsystemevent-was-not-fired-when-session-timeout" rel="self"></atom:link><language>en</language><lastBuildDate>Tue, 23 Apr 2019 03:57:53 -0400</lastBuildDate><item><title>Answer by Reguel Wermelinger</title><link>https://answers.axonivy.com/questions/3776/ivy-workflowsystemevent-was-not-fired-when-session-timeout/3780</link><description>&lt;p&gt;I can reproduce that the task state event is fired also on session timeouts. However, I see that in this case chances are pretty high that you  face an &lt;code&gt;EnvironmentNotAvailableException&lt;/code&gt; as many ivy APIs rely on a running Session, ProcessModelVersion and Task. Could it be that you have the same exceptions in your logs and therefore your listener code was not really executed?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Reguel Wermelinger</dc:creator><pubDate>Tue, 23 Apr 2019 03:57:53 -0400</pubDate><guid>https://answers.axonivy.com/questions/3776/ivy-workflowsystemevent-was-not-fired-when-session-timeout/3780</guid></item></channel></rss>