An Application Message Notification stuck in 'Waiting' state (originally failed due to a malformed recipient email address) was corrected and the message was suspended and resumed, but it goes right back into the same problem state — is there a way to actually retry it with the corrected data?

All FAQ questions / Integrations and APIs

Answer

Retrying a message resends it with its ORIGINAL Message Input Data — retrying doesn't pick up any correction made after the message was already generated, which is why suspending and resuming didn't help. To actually get the corrected data to send, the process/event that originally triggered the notification needs to be re-run from scratch, which generates a brand-new Application Message carrying the corrected input data — if that new input data is now valid, the new message should process successfully where the old stuck one couldn't, since it was permanently tied to its original (bad) data.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Integrations and APIs questions