When a message doesn't run successfully, you can troubleshoot the message. You have several options to troubleshoot a message. You can, for example:
Validate the message setup.
Run a message for testing and troubleshooting purposes.
Analyze the message history.
Analyze the file history, if the message has an Azure file storage connector with file actions.
Analyze the tracer, if you have used the tracer on the message run.
Common issues on the message are:
Field mapping sequence: Make sure the fields are mapped in the same sequence as shown on the related form in D365 F&SCM.
Mapping conditions and field conditions: Conditions limit the records that are processed. So, if records are skipped unexpectedly, check if conditions are defined.
Key field setup: Key fields are used to find and update records. If records are not updated unexpectedly, verify if the correct fields are marked as key fields.
Note
If you click a ‘Monitor …’ shape in the flow diagram, the related section or article in Operation > Monitoring integrations > Monitor integration - Details is opened.