I have a flow set up to read my emails and make a report to be sent to slack. The application Action step reads my email but pulls the wrong timestamps the email was sent. Either 4 hours before or 4 hours after. For Example it tells me the email was sent 6:00 PM but it was sent at 2:00 PM when I look in my inbox. I specifically mentioned to pull the time in EDT but for some reason it doesn’t pull the right data . The email connector feels insanely inconsistent when its connected with flow. I want to disconnect it and connect it again to refresh it but I believe this function is blocked for amazonbi Accounts. Any suggestions here ?
Hi @Mohamed_Anwer. Thanks so much for posting your question on the community. We have shared your message with our PM and SA team asked them to take a look at this/advise on any next steps.
Hi @Mohamed_Anwer,
This is an interesting case you found, a couple of suggestions I would recommend are, first, instead of asking the Flow to pull times “in EDT,” try explicitly instructing it in the prompt to convert the timestamp by subtracting 4 hours from the value the connector returns. Being explicit about the math tends to be more reliable than asking it to interpret time zone labels.
Alternatively, you could add a step after the email action that reformats the timestamps, something like “Take the email sent time and convert it from UTC to Eastern Daylight Time (UTC-4) before including it in the report.”
We noted that another user with an amazon bi account ran into a similar outlook connector issue, we are unsure at this time if this is an internal issue, so I would suggest either reaching out internally to your team and/or creating a support ticket (here is the link: Case management - AWS Support).
Hope this helps and feel free to keep us in the loop with any new updates!
I am having a similar issue. When I run the outlook connector in Chat it works fine. However, when I run it as part of my automation, it sometimes works, sometimes it does now. I removed the time constraint and asked it to just report the emails in automation and it still failed. Here is the error detail supplied by Quick.
The specific error message is: “Unsupported type passed: Tue Jun 02 2026 16:33:22 GMT+0000 (Coordinated Universal Time). Pass options.convertClassInstanceToMap=true to marshall typeof object as map attribute.”
This appears to be a technical issue with how the system is handling date/time formatting when connecting to your Outlook account through this particular flow, even though your Outlook connector works fine in other contexts. The error suggests there’s a data serialization problem with timestamp handling.
Since the connector works in other parts of the system, this might be a specific issue with how this automation flow is configured to interact with the Outlook connector. You may need to contact support to resolve this technical issue with the email checking step, as it appears to be a system-level problem rather than a connectivity or authentication issue.