mirror of
https://github.com/corda/corda.git
synced 2024-12-19 04:57:58 +00:00
949489a117
Flows that were started with a client id would hang because it would retrieve the existing flow's future and wait for it to finish. But, because the flow has failed its flow init and not saved its initial checkpoint, it is relying on `startFlow` to start the flow again (by redelivering the start flow external event). `FlowWithClientIdStatus` now holds the flow id that it is related to. This is then checked in `startFlow`. If a matching client id is found for a flow start, it then checks the flow id as well. If the flow id matches, then it lets the `startFlow` call continue, allowing it to actually start the flow again (how a flow without a client id would retry in this situation). |
||
---|---|---|
.. | ||
capsule | ||
djvm | ||
src | ||
build.gradle |