Dynamics Community Forum Thread Details

Supplier communication agent - not working

Hi All,

We configured the Supplier Communication Agent (SCA) in D365 Finance & Operations around 7 months ago by following Microsoft document and fast track videos. At that time we tested for 'Emails from vendors' scenario, it worked fine.

Now , later when a po confirmation mail is sent to configured mail box, the flow - Speed up updates in purchase orders using a Supplier Communications Agent
and it extracting the information from mail body and passing it to the - Supplier Communications Agent - inbound copilot agent.

1.But the mail which sent to configured mail is not coming to the - Follow up emails form in d365 fo.

2.I checked all the supplier communication agent configuration and set up, everything seems to good still not getting that mail into d365 F&O.
3.And we have enabled pay as you go for copilot studio
4.still not able to get why the emails not coming to the d365 fo, is there anything need to check.

Categories:

Dynamics 365 Finance

Problems I observed while troubleshooting the supplier communication inbound process (when a new email arrives from a vendor):

Speed Up Updates in Purchase Orders with Supplier Communications Agent — This is the initial flow. It fetches records from Dataverse at 1-hour intervals. For example, if the flow runs at 1:00 PM, it retrieves records created or updated between 12:00 PM and 1:00 PM.
After retrieving the records from Dataverse, the flow checks whether the selected email record has already been staged. If it has not been staged, the process continues with further steps.
In the next step, the flow again verifies whether the fetched Dataverse record needs to be staged or if it has already been staged.

This is the entire 1st flow :

Input to the API call :

Output:

4.In the above step, the API response returns true it allowing the process in the first flow to continue.
msdyn_PurchCopilotInboundShouldStageEmailCustomAPI_isValidForStaging,

The first flow successfully validates the record and completes the subsequent processing steps.

2.this is 2nd flow - (Self Heal) Speed up updates in purchase orders with Supplier Communications Agent.

In the second flow, the system again checks whether the same Data verse record has already been staged. During the first flow execution, the record was not staged, so the API returned true and the processing was completed successfully. However, when the second flow performs the same validation, the record has already been processed/staged, causing the API call to return false, as shown below.
This is my understanding during my troubleshooting process.