There is no known bug. In this case `in.notificationTaskId` is wrong? notificationTaskId is the id of the task that is ready to be processed by the user. Some pitfalls: 1. When you click on the link in the mail, then you go directly to the task. And if there is nothing to do, the task is done, which will redirect you to the task list. And there you may have still some other tasks. But you won't see the notificated task. 2. Do you have the right permissions/roles to see the necessary tasks in the task view? In the JsfWorkflowUi the url will be build as follows: #{facesContext.externalContext.requestContextPath}/pro/#{data.task.fullRequestPath}?taskId=#{data.task.id}follows: `#{facesContext.externalContext.requestContextPath}/pro/#{data.task.fullRequestPath}?taskId=#{data.task.id}`

There is no known bug. In this case `in.notificationTaskId` is wrong? notificationTaskId is the id of the task that is ready to be processed by the user. Some pitfalls: 1. When you click on the link in the mail, then you go directly to the task. And if there is nothing to do, the task is done, which will redirect you to the task list. And there you may have still some other tasks. But you won't see the notificated task. 2. Do you have the right permissions/roles to see the necessary tasks in the task view? In the JsfWorkflowUi the url will be build as follows: #{facesContext.externalContext.requestContextPath}/pro/#{data.task.fullRequestPath}?taskId=#{data.task.id}