Upon creating a job instance a rather big number of meta data will be created. It can be very useful in the development/debugging phase of the life cycle of the workflow. However it may prove to be extremely unfavorable in case of a mass parameter sweep calculation in a trusted environment, where the user interested only in the output and does not want to pay an extra price for dragging and storing of large amount of useless data.
Suggestions:
Minimal solution:
A new "Suppress producing meta data" check box in the workflow submission dialog.
More sophisticated solutions can be done by job level control for the blocking of meta data production (job configuration) or the association the production of meta data to user roles.
Certainly the suppression intention of the user should be overruled by the run time system in case of a run time error.