I have a process that involves a series of sensor data incidents which take the form of user tasks to lead to various service tasks being launched. Trouble is the service tasks need to know which incidents caused them to be launched. Simply looking at the history won't work because different incidents may be triggering different service tasks, even simultaneously (or close to). Is there a way for the service task to be passed information related to the previous state(s) that led to it's invocation, or the execution ID's/task ID's that caused it's invocation. Alternatively is there a way for the service task to be able to look back at the previous state(s) somehow to identify which paths led to the invocation so that those tasks could be queried?