I'm currently having a problem with the TokenTransactionSynchronizer. I'm using continuations, and I call

Code:
if (!context.inTransaction(true)) {
//do error handling
}
after this call executes, the txToken parameter has been removed from flowScope. At this point, I've entered an end state. But when I go back (using back button) and resubmit, the txToken is BACK in the flowScope.

I looked into the code, and it seems because I enter an end state, the FlowSession is popped from the FlowExection's Stack, and therefore the FlowExecutionManager doesn't save it to the storage...

I guess I need to use a different type of TransactionSynchronizer, one that doesn't use the FlowScope. It just seems weird that even if I'm using Continuations, changes I make to attributes in the FlowScope won't be saved to storage if I enter an end state.