Kepler

I'm still trying to isolate the problem, but I'm finding that a RecordToken is not "fully" being written to provenance.
When I run in the GUI I see that the token has two port_event rows: one with a write_event_id=-1 and another with a write_event_id that corresponds to the previous row.
When running from the commandline I only see the write_event_id = -1 row and nothing else.

The recordToken is being passed to a display actor - perhaps the non-GUI filter is removing that connection and the port firing is modified? That's my only lead so far...

I will try to make a simpler workflow to isolate it.