I'm having troubles trying to retrieve instances of processes when they are created with LiveCycle API using ServiceClient.invoke(invocationRequest).

As far that I can see, process instances are created correctly (I can manage them in LiveCycle AdminUI and in LiveCycle Workspace), but I can't retrieve them using TaskManagerQueryService.processInstanceList(...) or TaskManagerQueryService.processSearch(...), as process instances are simply missing... the strange thing is that process instances created with LiveCycle Workspace are returned correctly.

I found some additional information: debugging sql queries performed by LiveCycle apis, I found that TaskManagerQueryService.processSearch(...) always applies a filter to check if the user used to perform the search, has performed at least a task for an instance (it apply an sql filter on tb_queue.workflow_user_id joining it on tb_assignment, tb_task and tb_process_instance), even if this behavior isn't documented on javadoc. This means that, in contrast with workspace that starts a process using a human task, if the process is started using api, the initial human task isn't created, and TaskManagerQueryService.processSearch(...) will never return the started instance until the user has performed some other task on it...

Is there a workaround that could allow me to skip the "user interaction" check performed by the api, or at least, a way to start a process like the workspace using the initial human task?