I have a Zap that is published that takes an Outlook email in a Shared Mailbox, does some other stuff, and then delays for a set time and then sends an email as another user. it’s working great for a 1 hour delay while testing, but I will want to eventually change this delay to be 3 business days. The email needs to basically act as a forward of the first email with all the attachments in tact.
What I see when I return to the zap to work on it again is that if I try using the same test email I had loaded say a day before, it will give me errors in my subsequent steps, because it seems like either the hydrated attachments, or the email itself will expire. I’m wondering if this is just behavior for test records or if this will fail when I increase the delay in live as well.
I’m getting conflicting answers from Microsoft documentation and from Copilot inside the Zap for this. It suggests creating a Zapier table record to store the hydrated attachment and then retrieve from the table later. I’d rather not add the additional steps if they are unnecessary, but I’d also rather not wait to see



