title: Actionable Messages sometimes are not parsed correctly
body: <p>We've got reports that sometimes actionable messages are not displayed correctly by some clients. It doesn't matter if they message is displayed on Outlook OWA or Outlook Desktop app.</p>
  
  <p>I asked one of the clients to install Actionable Message debugger app and check the diagnostics section and others. Here are some details I've managed to read off from it:</p>
  
  <ul>
  <li>No card is attached to this message.</li>
  <li>Actionable messages processing has not been performed on this message. Actionable messages are only enabled for Office 365.</li>
  <li>Adaptive card payload found but could not be parsed. Please validate the payload.</li>
  </ul>
  
  <p>And diagnostics section:</p>
  
  <pre><code>"CardEnabledForMessage": false,
  "ClientName": "OutlookWebApp",
  "ClientVersion": "16.2528.7.2602797",
  "InternetMessageId": "&lt;ID&gt;",
  "Error": "EntityDocument does not exist.",
  -
  "AdaptiveCardPayload": {
      "found": true,
      "type": "AdaptiveCard"
  },
  -
  "MessageCardPayload": {
      "found": false,
      "type": null
  },
  -
  "AuthHeader": {
      "results": "&lt;address&gt;; dkim=none (message not signed) header.d=none;&lt;address&gt;; dmarc=none action=none header.from=&lt;address&gt;;",
      "authAs": "Internal"
  }
  </code></pre>
  
  <p>Up until recently, I wasn't able to reproduce the issue on my end. During some tests, I've sent myself a test message and it has not been parsed correctly. 
  When I sent another test message afterwards, it was working perfectly fine.</p>
  
  <p>Of course after comparison of both messages' sources yielded that both sources were identical. Headers were a little different but mostly in time and what appears to be the server. Diagnostics and error sections from debugger are almost identical.</p>
  
  <p>The method we use is SMTP (<a href="https://stackoverflow.com/questions/52076068/actionable-messages-not-displaying-regional-utf-8-characters">there were some issues with EWS</a>) and we're thinking of switching back if that causes the issue.</p>
  
  <p>Is there something that can be done in regards to this issue? It's probably worth noting that the payload we send is quite 'heavy' (as in, we had to limit ourselves with the amount of data we send because we were hitting something what looked like size limit)</p>