Hi benjamin.
We checked that issue and it turns out that you see a combination of two bugs 😉
1.) When using the node name as id for the BPMN 2.0 XML we run into the risk of creating invalid node names with spaces in your case (if you rename the nodes in the Model to "'Handle_vacation_request" it should work). We will fix that in trunk by encoding the node correctly.
2.) Known issue: If one content representation (the tabs in cycle) fails, none of the representations is shown. In this case the "developer friendly" view blocks your Image. We want to tackle that as well, but not sure if we will have the time this iteration. But we have it on the list!
Hope that helps?
Cheers
Bernd