Resilient Multi-Participant Workflow Orchestration: State Synchronisation and Failure Recovery in Enterprise Applications

Enterprise applications typically include processes that require multiple parties to work together to conduct business transactions․ Conventional workflow applications are designed to help a single party conduct business transactions but do not provide tools to help multiple parties work together․ Examples of processes with multiple parties include those in the financial and insurance industries and in health care authorization and other health care services‚ procurement‚ and hiring․ Other processes with multiple parties also exist․ In these and other multiple-party processes‚ each party performs tasks to help complete an overall business transaction․ Problems and needs particular to multiple-party processes that are not addressed by conventional single-party workflow applications include differences in the pace at which multiple parties work‚ loss of other parties' contact information‚ incomplete or incorrect work by other parties‚ and other problems documenting the overall business transaction․ This article provides information about designing multi-orchestration process models with features such as fully asynchronous participant interactions‚ multiple concurrent process instances‚ shared process data‚ failed participants‚ and other changing orchestration conditions․ This article recommends designing an additional state model and process events to manage participant interactions in your orchestration process․ An additional state model and process events can help prevent conflicts between participant and shared process data․ This article also provides information about ways to separate participant and process data for independent participant interactions‚ assign tasks to failed or unavailable participants‚ and restrict participant access to process data and tasks․ Enterprise financial applications are major case examples in this paper․ Other applications‚ such as health and insurance claims processing‚ government services‚ and enterprise approval processes‚ are mentioned․ Key design factors for complex‚ multistep processes in this paper include strategies for splitting and coordinating process steps and reducing the effects of errors in an orchestration environment․ Technology decisions are less important than these design factors

Authors

Publication Details

Journal
East African Journal of Information Technology
Published
2026-11-18
DOI
https://doi.org/10.37284/eajit.9.3.6323
Primary Topic
Business Process Modeling and Analysis
Type
article
Field-Weighted Citation Impact
0.00
Controls
|||
ALL TIME
JAN
FEB
MAR
APR
MAY
JUN
JUL
AUG
SEP
OCT
NOV
article

Resilient Multi-Participant Workflow Orchestration: State Synchronisation and Failure Recovery in Enterprise Applications

Mohammed Sayerwala
1 links
East African Journal of Information Technology
Business Process Modeling and Analysis
article

Resilient Multi-Participant Workflow Orchestration: State Synchronisation and Failure Recovery in Enterprise Applications

Mohammed Sayerwala
article en

Abstract

Enterprise applications typically include processes that require multiple parties to work together to conduct business transactions․ Conventional workflow applications are designed to help a single party conduct business transactions but do not provide tools to help multiple parties work together․ Examples of processes with multiple parties include those in the financial and insurance industries and in health care authorization and other health care services‚ procurement‚ and hiring․ Other processes with multiple parties also exist․ In these and other multiple-party processes‚ each party performs tasks to help complete an overall business transaction․ Problems and needs particular to multiple-party processes that are not addressed by conventional single-party workflow applications include differences in the pace at which multiple parties work‚ loss of other parties' contact information‚ incomplete or incorrect work by other parties‚ and other problems documenting the overall business transaction․ This article provides information about designing multi-orchestration process models with features such as fully asynchronous participant interactions‚ multiple concurrent process instances‚ shared process data‚ failed participants‚ and other changing orchestration conditions․ This article recommends designing an additional state model and process events to manage participant interactions in your orchestration process․ An additional state model and process events can help prevent conflicts between participant and shared process data․ This article also provides information about ways to separate participant and process data for independent participant interactions‚ assign tasks to failed or unavailable participants‚ and restrict participant access to process data and tasks․ Enterprise financial applications are major case examples in this paper․ Other applications‚ such as health and insurance claims processing‚ government services‚ and enterprise approval processes‚ are mentioned․ Key design factors for complex‚ multistep processes in this paper include strategies for splitting and coordinating process steps and reducing the effects of errors in an orchestration environment․ Technology decisions are less important than these design factors

East African Journal of Information TechnologyVol. 9(3)
Business Process Modeling and Analysis
AI Navigator

Ask Laika to Summarize, Analyze, and Connect papers live on the map.

Summarize Papers & Methodologies

Extract key findings, datasets, and comparative methods across publications.

Benchmark Rankings & Visual Analytics

Rank top research institutions, authors, funders, topics, and journals by Field-Weighted Citation Impact (FWCI) and paper volume with instant charts.

Connect Distant Disciplines

Bridge topological clusters on the map to find hidden collaborative intersections.

Laika access coming soon