Create Asset on Zapier is broken?

Hi all,

Notice today that my automation is broken? When creating a duplicate of an asset it makes a file that’s stuck being queued/uploaded.

It’s been working fine for over a year, has something changed? I’m not on the new API/frame version.

Thanks!

Are you copying the asset using our copy asset endpoint or are you creating a new one and using the original URL from the first one as the source for the second asset?

Hi @jhodges , Thanks for replying! Hope you’re well :slight_smile:

I believe I’m using your endpoint and copy the file based on the triggered asset. I.e When set to approved, create that asset into X folder.

That looks like it should work. Can you show me what the trigger is for this further up in your Zap? There’s a small chance that the original is not yet actually available depending on when in the asset lifecycle this flow is triggered.

Looking at the zap history, there is a link and when copied into a browser it does supply a working file. I’ve had this automation for over a year and this hasn’t been an issue but in the last 24hrs it’s stopped working.

Has there been any changes on your end?

@jhodges happy friday!

Just trying again to troubleshoot this, I’ve tried adding a delay and adding a find asset step to give the process time to develop the original. But still having the same issue.

Do you have any suggestions? Thanks!

I looked into yesterday’s API release to see if there were any changes that went out which had the potential to impact what we call “remote uploads” which you’re leveraging here via Zapier and there was a small change but it shouldn’t have affected anything.

I’ll do some more testing today to try and reproduce the issue and will get back to you once I know more!

Thanks @jhodges, appreciate it! Have a nice weekend :slight_smile:

I’ve spoken with engineering and they confirmed the release that I was worried about was indeed the source of the regression affecting your uploads here.

The team has a fix ready to go which should go out in the next hour or so!

1 Like

@jhodges all working now, thank you!

1 Like