@borinocap the spaces might be the culprit here. I added spaces into a file name (the DRYP one) and I ran into the same errors. Standby.
1 Like
Hmm Iām now unable to reproduce this on my end. I added additional logging to try to catch it and now I canāt. I even added spaces in the beginning.
Any chance you can reach out to Zapier support and provide them the URL of your zap (send them the url in your browser) and ask them to pull the logs for that? That should help me figure out whatās going on for you vs me.
The email I got from Zapier stated Skipped run because of missing_state which seems like a Zapier issue and not Frame. What was the error you got in your email about the error?
From Zapier Support:
ā
Frame Authentication Bug
First, regarding the Frame issueāthere is indeed a bug with Frameā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ās authentication refresh randomly fails, affecting any Frame action regardless of your Zapās configuration or timing. This bug has been logged and is up to Frame/Adobe to fix.
ā
I have learned that if you replay the zap that it will run successfully, its when it hasnāt ran for several hours that the tasks will error out.
I have been updating my zap versions and still run into the issue - thanks @leafy.link for getting some clarity from Zapier. @CharlieAnderson let us know when we can be on the lookout for a fix for this and I can update you if the issues continue or not. Thanks!
@jesse I just pushed out a new update today to help with handling token refreshes (1.1.9). We were only using Zapierās built in token refresh logic previously (autoRefresh: true) but I added more logic to help keep the connection alive on our side.
Could you try 1.1.9 and see if that helps solve your issues?
I am not good talking about something I do not know about, but I think I found a simple fix to resolve the issue.
https://www.loom.com/share/5f2f1a1f37c8434180f30226c44a72d8
Yep, if Frameio doesnt send out a forced update, then that is the only way to update to the latest version - manually on a zap by zap basis.
@CharlieAnderson will move to 1.1.9 and let you know 
@jesse thanks! Please let me know if that helps!
@leafy.link Iām glad you got it working, sorry for not explaining that a bit more in depth (versioning that is).
We donāt force migrate users unless thereās a major issue that needs to be resolved as forcing migrations could break a lot of peopleās workflows if there are breaking changes for whatever reason.
That said, if 1.1.9 helps fix the auth issues we will consider migrating all users if it makes sense as we definitely donāt want users having their zaps stall out for auth issues/reasons.
Also @jesse please be sure to re-connect your account to the latest version.
When adding Frame as an Action or Trigger, under Account click Change and then + Connect new account and log in again. This will be sure to use the most up to date version (and it should show connected to 1.1.9)
hi @leafy.link can you try the latest version, 1.1.9, as that has the new token refresh logic in it
hi @mdkn thanks for the update. This will warrant more investigation as to why this is happening as itās more complicated and involved than refresh token logic.