This was a bug in the initial release of the workflow modeler client prior to 6.7.1 SP1. Is this happening with a recent version of the client?