Similar to an older post, I ran into the same situation but have some more context and a more specific question.
The ‘Invoice Payment Link Update’ is a straightforward quality of life process that triggers the payment link of an invoice to update when an invoice becomes ready for synchronization; very nice - clicks saved. However, we are seeing this out-of-the-box Business Event fail regularly.
Digging into the notification itself in the Process Push Notifications screen, I noticed that every failed push notification JSON looks roughly like this:
{Inserted values: {{INV: 000010}{needs_sync: true}, {INV: 000011}{needs_sync: true}},
Deleted values: {{INV: 000010}{needs_sync: false}, {INV: 000011}{needs_sync: false}},
Timestamp: 539096372739445064}
Does two+ records being updated at the same time in the same notification cause business events with the ‘Trigger by Record Change’ to fail? Is there a different configuration to avoid this overloading? We regulary receive and process payments which cover multiple invoices so this situation is common. I see similar notifications failing for other events I’ve created, so it seems like an issue that goes beyond this one event.
Version 24R2
