Problem Faced:
When adding or removing the party contact in the XCRO 5.x we are observing the error message: Party update is in progress
FLOW:
Replication Steps:
1. Created a party using an existing customer ID.
2. Added a contact
3. Approved it.
4. Navigated to 'summary' and tried editing the approved party
5. Observed the same error "Party update is in progress"
Note: This is a known issue where an API call is being missed.
Observation:
observed that the customer was successfully able to approve the deal after adding the new party. However when we navigated to the party maker and checker we observed the party to be missing from the queue. In order to address this concern I gave you a few queries to run on the db. Please find the respected query and their outputs mentioned below:
Query: xcro-db> db.mdm.parties.find({_id: "P3128"})
Output:
[
{
_id: 'P3128',
name: 'ORIGO COMMODITIES INDIA PRIVATE LIMITED ESCROW AC',
customerId: '35111571',
internal: true,
refId: 'ESC010566200000408',
isNeutral: false,
draft: false,
_metadata: {
lastUpdated: ISODate('2025-12-18T13:03:27.257Z'),
createdAt: ISODate('2025-07-02T12:53:16.892Z'),
deleted: false,
version: { document: 3, _id: ObjectId('68652bbcc5c0c75d3fb5542c') },
_id: ObjectId('68652bbcc5c0c75d3fb5542b')
},
__v: 0,
workItemId: 'PD1453'
}
]
----------------------
Query: db.mdm.parties.draft.find({partyId: 'P3128'})
Output:-
[
{
_id: 'PD1453',
operation: 'U',
status: 'PDNG',
partyId: 'P3128',
basic: {
_id: 'P3128',
name: 'ORIGO COMMODITIES INDIA PRIVATE LIMITED ESCROW AC',
customerId: '35111571',
internal: true,
refId: 'ESC010566200000408',
isNeutral: false,
draft: false,
_metadata: {
lastUpdated: '2025-07-02T13:08:29.608Z',
createdAt: '2025-07-02T12:53:16.892Z',
deleted: false,
version: { document: 1, _id: '68652bbcc5c0c75d3fb5542c' },
_id: '68652bbcc5c0c75d3fb5542b'
},
__v: 0
},
accounts: [
{
_id: 'partyAccounts1859',
partyId: 'P3128',
description: '',
paymentInstrumentId: 'internal',
paymentDetails: {
accountNumber: '010566200000408',
name: 'ORIGO COMMODITIES INDIA PRIVATE LIMITED ESCROW AC'
},
_metadata: {
lastUpdated: '2025-07-02T12:53:37.150Z',
createdAt: '2025-07-02T12:53:37.119Z',
deleted: false,
version: { document: 1, _id: '68652bd13935e1bc890e5c1d' },
_id: '68652bd13935e1bc890e5c1c'
},
__v: 0
}
],
contacts: [
{
name: 'SUNOOR KAUL INP',
email: 'skaul@origoindia.com',
mobileNumber: '9160901277',
workPhone: '',
designation: 'INP',
address: { street: '', country: '', state: '', pincode: '' }
},
{
name: 'MAYANK DHANUKA INP',
email: 'mdhanuka@origoindia.com',
mobileNumber: '9650012853',
workPhone: '',
designation: 'INP',
address: { street: '', country: '', state: '', pincode: '' }
},
{
name: 'RAMANATHAN A AUTH',
email: 'ramanathan.a@samunnati.com',
mobileNumber: '8925527232',
workPhone: '',
designation: 'AUTH',
address: { street: '', country: '', state: '', pincode: '' },
_id: ''
},
{
name: 'APPARAJU KISHOREKUMAR AUTH',
email: 'kishorekumar.a@samunnati.com',
mobileNumber: '9705653713',
workPhone: '',
designation: 'AUTH',
address: { street: '', country: '', state: '', pincode: '' }
}
],
documents: [],
interaction: {
lastModifiedBy: 'akash.kumar18@yes.bank.in',
lastModifiedOn: '16-Dec-2025 05:45 PM',
lastApprovedBy: 'kumari.priya1@yes.bank.in',
lastApprovedOn: '16-Dec-2025 05:48 PM',
state: 'END'
},
interactionHistory: [
{
userId: 'akash.kumar18@yes.bank.in',
userName: 'Akash Kumar (OSD)',
role: 'PARTYMAKER',
action: 'Create',
time: 1765886363,
timeStamp: '16-Dec-2025 05:29 PM',
review: ''
},
{
action: 'Submit',
userId: 'akash.kumar18@yes.bank.in',
userName: 'Akash Kumar (OSD)',
role: 'PARTYMAKER',
time: 1765887342,
timeStamp: '16-Dec-2025 05:45 PM'
},
{
action: 'Approve',
userId: 'kumari.priya1@yes.bank.in',
userName: 'Kumari Priya (OSD)',
role: 'PARTYCHECKER',
time: 1765887499,
timeStamp: '16-Dec-2025 05:48 PM',
review: { username: 'Kumari Priya (OSD)', note: 'ok' }
}
],
_metadata: {
lastUpdated: ISODate('2025-12-16T12:18:19.430Z'),
createdAt: ISODate('2025-12-16T11:59:22.732Z'),
deleted: false,
version: { document: 8, _id: ObjectId('6941499ac0578772990aa32a') },
_id: ObjectId('6941499ac0578772990aa329')
},
__v: 7
}
]
-------------------------
Query: db.bpm.PartyManagement.find({_id: 'PD1453'})
Output:-
[
{
_id: 'PD1453',
processName: 'PARTYMANAGEMENT',
processId: 'PD1453',
inProgress: false,
state: {
tokens: [
{
position: 'END',
owningProcessId: 'PD1453',
_id: ObjectId('6941499abfd9eab9f52d7ad7')
}
]
},
history: { createdAt: 1765886362749, historyEntries: [] },
properties: {
read: false,
lastOpened: 1765887361164,
lastClosed: 1765887518980,
interactions: [
{
openedBy: 'akash.kumar18@yes.bank.in',
openedAt: 1765886362778,
openedState: 'PARTYMAKER',
name: 'Akash Kumar (OSD)',
closedBy: 'akash.kumar18@yes.bank.in',
closedAt: 1765886362803,
closedState: 'PARTYMAKER'
},
{
openedBy: 'akash.kumar18@yes.bank.in',
openedAt: 1765886364092,
openedState: 'PARTYMAKER',
name: 'Akash Kumar (OSD)',
closedBy: 'akash.kumar18@yes.bank.in',
closedAt: 1765886457935,
closedState: 'PARTYMAKER'
},
{
openedBy: 'akash.kumar18@yes.bank.in',
openedAt: 1765886543060,
openedState: 'PARTYMAKER',
name: 'Akash Kumar (OSD)',
closedBy: 'akash.kumar18@yes.bank.in',
closedAt: 1765886583320,
closedState: 'PARTYMAKER'
},
{
openedBy: 'akash.kumar18@yes.bank.in',
openedAt: 1765887175341,
openedState: 'PARTYMAKER',
name: 'Akash Kumar (OSD)',
closedBy: 'akash.kumar18@yes.bank.in',
closedAt: 1765887342364,
closedState: 'PARTYMAKER'
},
{
openedBy: 'kumari.priya1@yes.bank.in',
openedAt: 1765887361164,
openedState: 'PARTYCHECKER',
name: 'Kumari Priya (OSD)',
closedBy: 'akash.kumar18@yes.bank.in',
closedAt: 1765887518980,
closedState: 'PARTYCHECKER'
}
],
reviews: [
{
username: 'kumari.priya1@yes.bank.in',
currentState: 'PARTYCHECKER',
timeStamp: 1765887499403,
note: 'ok',
comments: null
}
],
procUnit: [],
makers: [],
checkers1: [],
checkers2: [],
checkers3: [],
opened: false
},
_metadata: {
lastUpdated: ISODate('2025-12-16T11:59:22.752Z'),
createdAt: ISODate('2025-12-16T11:59:22.751Z'),
deleted: false,
version: { document: 1, _id: ObjectId('6941499abfd9eab9f52d7ad9') },
_id: ObjectId('6941499abfd9eab9f52d7ad8')
},
__v: 0
}
]Analysis:
Analyzing the above outputs we can observe that their is a workItemId: 'PD1453' present for the concerned party which is only present for the party which is not created or is in the process of approval, also we checked the collections "dealLive.deals.parties" and "dealDraft.deals.parties" and observed that no related workItem is present for this _id: 'P3128'.
After a proper offline investigation we have come to a conclusion that this improper creation of the workItemId even after the approval of the deal and the party was due to a network error. In other words, this is an intermittent issue which could arise due to the presence of some jitters in the network connection.
Resolution:
Moving forward, in order to resolve this concern I have prepared and internally tested three Curl commands for the following purpose:
1. Approve Draft
2. Clear workItemId
3. Delete BPM WorkItem
Please find the commands mentioned below:
Status update from PDNG --> APVD
curl -X PUT "http://mdm.<namespace>/api/v1/parties/draft/update/P3128" \
-H "Content-Type: application/json" \
-d '{
"status": "APVD"
}'
-------------------------------------------------------------
Updating workItemId to NULL
curl -X PUT "http://mdm.<namespace>/api/v1/parties/update/P3128" \
-H "Content-Type: application/json" \
-d '{
"workItemId": ""
}'
--------------------------------------------------------------
Deleting from bpm.PartyManagement
curl -X DELETE \
"http://bpm.<namespace>/api/v1/workflows/PartyManagement/workItems/PD1453"
Once We run these commands we will be able to remove the workItemId and hence the issue will be resolved.
Lastly in order to run these commands you may exec into the bff pod/component and trigger these curls.
I hope the above information was helpful, In case of any further queries or concerns, please feel free to write back to me, I'll be more than happy to assist.
Have a great day ahead and stay safe :)
Regards,
S.M.Hammad
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article