I think the issue is still in JBPM 5.4 as well.
Redeploying the application does not look like an elegant solution but solution nonetheless.
Reply to this message by going to Community
Start a new discussion in jBPM at Community