June 23, 2020
In our most recent Corda 4.5 release, we announced new enhancements to our flow management capabilities:
If a node user terminates a flow, counter-parties are automatically notified and any soft-locked states in the vault are automatically released.
Generally, operating a system requires multiple subsystems to function collectively and simultaneously. Occasionally, the systems do not work at the capacity they are supposed to which would require intervention by a system operator to recalibrate the system in order to restore optimal performance. In Corda, this process is referred to as flow management.
In Corda, a flow becomes problematic or unusable in situations where:
To resolve these issues, you can terminate a flow similar to how you would cancel a process.
In Corda 4.5, we have improved the existing killflow operation, so that:
That is, the flow termination becomes less brute forced, and the consequence of the termination is well handled.
Find more information at out docs site at: api-flows
Want to learn more about building awesome blockchain applications on Corda? Be sure to visit corda.net, check out our community page to learn how to connect with other CorDapp developers, or sign up for one of our newsletters for the latest updates.
— Peter Li is a Developer Evangelist at R3, an enterprise blockchain software firm working with a global ecosystem of more than 350 participants across multiple industries from both the private and public sectors to develop on Corda, its open-source blockchain platform, and Corda Enterprise, a commercial version of Corda for enterprise usage.
Follow us on twitter here.
Share this post
July 01, 2020
June 29, 2020
Stay up to date on the latest news and articles related to Corda.