@LuisB647 I would like to see the full automation. Specifically, what is the mail item that your properties are coming from? Your screenshot is cut off and only shows these properties being used. I suspect the problem is elsewhere in your automation.
I am going to pass you an automation where the same thing is happening, therefore, what it does is extract the body of the mail, later it stores it in a txt file, I added the sender property and the following appears, which is exactly what same as what is happening in the previous example
/O=EXCHANGELABS/OU=EXCHANGE ADMINISTRATIVE GROUP (FYDIBOHF23SPDLT)/CN=RECIPIENTS/CN=BC32D794D2414FEA9EE0424DE6CE2858-BUZON SCOTIScotiabank Colpatria InformaReporte de Ejecución 05/04/2022
Posted: 4 months ago
Posted: 8 Sep 2022 14:31 EDT
Thomas Sasnett (ThomasSasnett)
Lead Robotics Architect
I do not think this is an issue with the Outlook connector as it is based off of the Outlook Interop methods you can use to program against Office applications natively. If you do feel it is an issue solely in Pega Robotics however, I would suggest opening a support request. They can get on with you to confirm with whom the issue lies.