Frame Authentication Bug With Zapier

Automations Zapier
1

I have steps in Zapier that are failing from issues on the Frame-io end.
I have spoken to Zapier’s support about this, and they have indicated that it is on Frame-io’s end.
Here is what they said:
—
Frame Authentication Bug
First, regarding the Frame-io issue—there is indeed a bug with Frame-io’s authentication system where it intermittently fails to refresh connections properly. This causes the error “Request failed with status unknown” that you’ve been seeing in your folder creation and file upload steps. This isn’t me oversimplifying things, but rather the specific technical issue we’ve identified where Frame-io’s authentication refresh randomly fails, affecting any Frame-io action regardless of your Zap’s configuration or timing. This bug has been logged and is up to Frame/Adobe to fix.
—

I would like to add that from my understanding that Frame-io is a “Client” of Zapier, and their for is the one reasonable to uphold their keys and authentications with Zapier. The reason why I chose to use Frame-io was because it has integration with Zapier, because this seems to be false, from my eyes, I felt scammed and would like a reason why this is even an issue.

2

hi @leafy.link we use Zapier’s autoRefresh: true function with regards to our authentication. That said, our TTL is 14 days (Adobe IMS requirement, not Frame’s) and so if you dont have an action that fires within that 14 day window the auth will not refresh as it stands now.

That said, I am working on a better version that helps with keeping the connection alive on our side so we don’t have to worry about random disconnects.

3

@leafy.link I just promoted a new version, 1.1.9, which aims to add more robust refresh logic on our side as opposed to only relying on Zapier’s autorefresh. Try it out and lmk if it is working for you, has been working for me for the past week or so.

4

Issue is still happening