How to fix "Azure.RequestFailedException: Requested message could not be located.

Kunam, Umakanth 40

"Azure.RequestFailedException: Requested message could not be located. Couldn't find a record with the messageID: 404 (Not Found)\r\nErrorCode: MessageNotFound

I'm unable to find Triage of MessageId for the first time i'm getting above error, in second retry it is sending correctly, i just wanted to what causing this issue , i have reviewed the documentation no clues :

SnehaAgrawal-MSFT 21,771 Reputation points

2024-06-24T06:18:56.2133333+00:00

@Kunam, Umakanth Thanks for reaching here! Could you confirm, if you are trying to get the message status and the first request returned message not found and the second returned the correct response?
Kunam, Umakanth 40 Reputation points

2024-06-24T12:13:47.3466667+00:00

yes, in the first request it is showing this error, once it's failed it is going to exception level then it is working in exception.

Accepted answer

SnehaAgrawal-MSFT 21,771 Reputation points

2024-07-09T05:59:07.77+00:00

Antolovich, Junli , Kunam, Umakanth

Update-

After clarification with team its came out to be a known issue we are currently having.

Currently, we don't have an immediate fix for this, we're working on a longer term fix.

Its recommended to not use the automatic polling (using WaitUntil.Completed) for production ready workloads. Instead switch to using manual polling as shown in the example here: Quickstart - Manually poll for email status when sending email - An Azure Communication Services Quickstart | Microsoft Learn

We will also update quickstart with this recommendation as it doesn't currently mention this.

Hope this helps let us know.
Please sign in to rate this answer.
Kunam, Umakanth 40 Reputation points

2024-08-30T03:28:47.96+00:00

We tried by applying Manual poling after monitoring in different environments we are facing again same issue. please respond ASAP

SnehaAgrawal-MSFT 21,771 Reputation points

2024-09-10T05:38:52.7766667+00:00

Reached out to you privately.

Antolovich, Junli 20 Reputation points

2024-09-20T12:20:30.7966667+00:00

We tested around 2400 notifications in QA among them 80 notifications ended up with 404 errors, so the polling workaround does not solve the issue as reported by Kunam above
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

1 additional answer

SnehaAgrawal-MSFT 21,771 Reputation points

2024-06-24T14:41:18.6366667+00:00

@Kunam, Umakanth Thanks for reply! Looking at logs for that request. The send request was processed in the Central US region. The first request to get the status landed in East US. The get status request came in before the data could be replicated to the other region.

This can happen if the request for the status comes in to quickly as our service runs on multiple machines over different regions.

Let us know if you have further query.
Please sign in to rate this answer.
Antolovich, Junli 20 Reputation points

2024-07-01T20:51:39.4233333+00:00

Hello @SnehaAgrawal-MSFT , we encountered the same issue in our application, which utilize azure communication services - email services with this API call:

EmailSendOperation emailSendOperation = await _client.SendAsync(WaitUntil.Completed, emailMessage);

If the service is running on multiple machines over different regions, then if should have returned with correct status for the completed operation, instead of a 404 error.

Is this considered as an acceptable behavior? I believe this is a bug need to be fixed.

Antolovich, Junli 20 Reputation points

2024-07-02T16:23:31.09+00:00

Hello @SnehaAgrawal-MSFT ,

Please let us know if MSFT considers this as a bug. If so, can you please open a bug and provide ETA on when this issue will be resolved.

If not, we need to consider another email relay provider.

SnehaAgrawal-MSFT 21,771 Reputation points

2024-07-08T06:21:58.2933333+00:00

I have reached out to concerned team for further clarification.

Kunam, Umakanth 40 Reputation points

2024-08-30T19:46:03.02+00:00

We tried by applying Manual poling after monitoring in different environments we are facing again same issue. please respond ASAP

Kunam, Umakanth 40 Reputation points

2024-09-09T14:47:30.8866667+00:00

@Antolovich, Junli

did you find any breakthrough for above Bug?

Antolovich, Junli 20 Reputation points

2024-09-09T15:01:56.7033333+00:00

We implemented poling of the EmailSendOperation, and have not seen any issues during the testing. However, as Umakanth noticed, it's not a resolution. Microsoft is currently working on the final resolution

Kunam, Umakanth 40 Reputation points

2024-09-09T15:08:52.6+00:00

@Antolovich, Junli
From how many days you are monitoring?
we have implemented same suggested changes (manual poling), we are again facing this issue,
what changes you have made, can you please let us know here!

Kunam, Umakanth 40 Reputation points

2024-09-09T15:16:03.54+00:00

Thanks in advance

Antolovich, Junli 20 Reputation points

2024-09-09T15:26:52.4666667+00:00

We have not deployed the changes to production yet. We are still testing the solution, and thanks for sharing your result, so we are going to test it further, for coding we added similar to what Microsoft recommended: > /// Call UpdateStatus on the email send operation to poll for the status /// manually. try { while (true) { await emailSendOperation.UpdateStatusAsync(); if (emailSendOperation.HasCompleted) { break; } await Task.Delay(100); } if (emailSendOperation.HasValue) { Console.WriteLine($"Email queued for delivery. Status = {emailSendOperation.Value.Status}"); } } catch (RequestFailedException ex) { Console.WriteLine($"Email send failed with Code = {ex.ErrorCode} and Message = {ex.Message}"); }

Kunam, Umakanth 40 Reputation points

2024-09-09T15:38:45.7+00:00

the implementation, which is tested in test env, but still getting errors. please suggest me the changes to work

Antolovich, Junli 20 Reputation points

2024-09-09T15:47:14.97+00:00

This is what we have:

EmailSendOperation emailSendOperation = await _client.SendAsync(WaitUntil.Started, emailMessage);

// Call UpdateStatus on the email send operation to poll for the status

try

{

while (true)

{

await emailSendOperation.UpdateStatusAsync();

if (emailSendOperation.HasCompleted)

{

break;

}

await Task.Delay(100);

}

return ACSEmailMapper.MapFromACSEmailSendOperation(emailSendOperation);

}

catch (RequestFailedException ex)

{

throw new ApplicationException($"Email send failed with Code = {ex.ErrorCode} and Message = {ex.Message}", ex);

}

Kunam, Umakanth 40 Reputation points

2024-09-09T15:51:42.2+00:00

Is this working in the test or dev environment, before sending to production environment?

Antolovich, Junli 20 Reputation points

2024-09-09T15:53:57.8866667+00:00

works in dev and qa

Antolovich, Junli 20 Reputation points

2024-09-20T12:18:20.1733333+00:00

We tested around 2400 notifications in QA among them 80 notifications ended up with 404 errors, so the polling workaround does not solve the issue.

Kunam, Umakanth 40 Reputation points

2024-09-20T12:49:48.3066667+00:00

Hello @SnehaAgrawal-MSFT ,

Please let us know the workaround here, as we are unable to fix this issue. even after trying proposed manual poling solution.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

How to fix "Azure.RequestFailedException: Requested message could not be located.

1 additional answer

Your answer