With the message-store API json response, the SendingFailed faxes have a faxErrorCode that is usually Undefined. Is it possible with the API to view the failure reason as reported with the Call Log in the web interface eg Busy, No Answer, etc? I see there are many possible messages, but none with the above phrasing.
I am also having trouble seeing the multiple attempts for failed or repeated faxes even when specifying distinctConversations=false in the request. I don't know how the "conversation ID" match up to message ids, but I assume they are synonyms. How can I see the multiple attempts through the API request?
There was a previous suggestion to provide message ids through the Call Log, which could also work, but would not be ideal.