Skip to main content

We set up a zap to extract Linkedin form info so we can send it to CRM.
It has been running without any issue but recently it started to stop at the very first step. AI troubleshoot is suggesting the form_id missing but it always ran successfully without form_id.
The weird thing is when we rerun the zap, it goes through. is this an issue on Zapier side or Linkedin side?

 

 

Hi ​@meg1215,

 

Welcome to the Community.

 

If your Zap fails at the LinkedIn Ads trigger, it could be due to a temporary API issue or a change in LinkedIn's integration. Since the Zap runs successfully when manually triggered, it may be an intermittent problem. To troubleshoot, check LinkedIn Ads' API status, reconnect your LinkedIn account in Zapier, and verify that your LinkedIn form setup, including the form_id, is correct.

 

I hope this helps. Please let me know if you have any questions.


@JammerS 

thanks for the reply.

we reconnected the account. but the things still stay the same. In fact, not all the zaps get stuck. Majority of them goes through and some get stuck on the first step and when we replay them, they go through. I heard in the past similar thing happened due to hydration for linkedin zap or something. is this like a temporary error? last time, it resolved after a few days but it has been almost a week now. 


Hi ​@meg1215,

I did some digging into this, and it seems like the error that you’re running into is a known bug with the LinkedIn Ads integration. Our team is aware of the issue and is working on a fix. I've added your email address as another affected user. That does a few things:

  • Bring this to the attention of the integration developers
  • Help track and prioritize fixes
  • Allows us to notify you via email if/when this is fixed

Unfortunately, I do not have an ETA, but I’ve added you to the list of users affected by this issue so we can let you know as soon as we have any updates.

Hopefully, this helps.


Hey folks, I’m pleased to share that the bug has been fixed! 😁🎉

In case you missed the email notification that went out, here’s what you need to know:

We have made 2 changes to help with these errors:

  • Improved error messages - now you will see the HTTP error code and the error message returned from the API, which may help you troubleshoot the situation more easily.
  • Ability to opt out of retrieving extra details. Two new fields, Retrieve Creative Details, and Retrieve Campaign Details, have been added to the triggers. They are set to True by default. If you are experiencing "Error while hydrating data" in the future, you can try to turn off one or both of these. The "Error trying to fetch share data" relates to Retrieve Creative Details, for example. If you turn that to False, we will no longer make the extra call that is failing in your case. Please verify that you can still complete your workflow and all necessary fields for later steps are still present, as this will result in less data in each task.

As the bug is sorted we’ll be closing this topic now. If you’re still encountering issues, please post a new topic in the Community here or contact Support directly to let us know. In the meantime, happy Zapping! ⚡️


Reply