New LSID not propagating to provenance
This came up as a reporting bug, but that's a symptom if something larger. I'm not sure exactly where the system breaks down, but it looks like provenance isn't staying in synch with the current LSID. At least when you open a KAR from another computer in your own Kepler installation and then make a modification to it (this assigns a brand new LSID to the workflow).
When the workflow is executed after the change (and new LSID) the provenance DB still shows the execution as the old original workflow LSID.
Can you (dan) and aaron help narrow down where this is happening?