Hi
I raised an issue to improve this
opened 09:29AM - 25 Jun 18 UTC
closed 01:31PM - 16 Aug 18 UTC
Improvement
Currently, we only have a global catch for all the dispatches that are fired. Ev… en if just one of the dispatch operation fails the exception is almost meaningless for the end-user. There is no way you can troubleshoot and pin it down to the queue that does not exist based on the following exception message
```
2018-06-22 19:07:28.620 ERROR NServiceBus.Transports.SQS.MessageDispatcher Exception from Send.
Amazon.SQS.Model.QueueDoesNotExistException: The specified queue does not exist for this wsdl version. ---> Amazon.Runtime.Internal.HttpErrorResponseException: The remote server returned an error: (400) Bad Request. ---> System.Net.WebException: The remote server returned an error: (400) Bad Request.
at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
```
https://github.com/Particular/NServiceBus.AmazonSQS/blob/support-3.3/src/NServiceBus.AmazonSQS/MessageDispatcher.cs#L50
Further details
https://discuss.particular.net/t/amazon-sqs-queue-does-not-found-with-nsb7/626/4?u=danielmarbach
Until there is more transparency I would suggest you double check the routing code and check for casing mismatch. Amazon SQS queues and URLs are case-sensitive, unfortunately.
Regards