Hello there, ​@AeroZap!

Hmm, that’s very strange indeed. How big are the files? If it it was a particularly large file perhaps that caused an issue hydrating data from the file attachment—thinking it might have timed out due to the size? 

We don’t have access to the logs for your Zaps here so I’d really recommend reaching out to our Support team here to have this investigated further. They’ll be able to dig into the logs to see if there’s any additional information captured in the logs that might help to explain what’s causing the issue here.

Keen to ensure this gets sorted so please report back here to let us know how you get on with them—very curious to know what’s causing this! 

Just to follow up on my question. I contacted Support and after some troubleshooting it turns out it’s a bug in the newest version of the Code by Zapier action where the value of the Email Parser by Zapier’s Email Attachment property is not being correctly handled by the Code step’s input parameters, resulting in an invalid value being passed. My zap started failing on its own because these actions are sometimes auto upgraded to the newest versions, and mine was. I was able to “resolve” it by forcing a save/publish of the Zap from a version where it still had the Code by Zapier’s previous “un-upgraded” version. I was told I would be notified when the bug is fixed.

That’s great news, ​@AeroZap!  So glad the Support team were able to get to the bottom of what what causing the issue here!

Really pleased you were able to get this resolved in the meantime by publishing an earlier version of the Zap. We’ll keep you posted on the status of that bug report. Seems like you’re all set for the moment but if you run into any further issues in the meantime do let us know. In the meantime, happy Zapping!