Skip to main content

A zap that previously worked now hits an error. 
The step is ‘New Record (Saved Search)’ to poll for records in a particular state notified by a saved search.
The SS returns valid records. In the run details I get an expected record id, the correct Saved Search ID, then I expect all the fields and values of the specific record but get something called HOIST field with a long string. Appears zapier cannot read the json passed from netsuite to zapier or the response is empty.
Examining the rest execution log shows a sql query and a couple of jsons returned amongst them but no json with the custom record. I don't know the zapier process and what should go back and forth but there are a number of request and responses empty or just have ‘{ }’ s content. That feels not right. 

in Zapier i see 


I've reauthorized the netsuite connection and deleted browser cache as these were hints to resolve but no luck. All zap with that connector behave the same. No similar netsuite error found online in forums.

its a development in progress so I might/probably have changed the custom record or elsewhere something that might cause this netsuite behavior. 
for now I'm confused so if some of you wizards 😉 have any direction i could search for a resolution would be great.

thanks in advance for suggestions!


 

Hi ​@Waldorf 

Help links for using NetSuite in Zaps: 

https://zapier.com/apps/netsuite/integrations#help

 

You may want to try opening a ticket with Zapier Support: https://zapier.com/app/get-help


Hi ​@Troy Tessalone 

thanks for the assistance, got it resolved though.

It is a permission issue.
The processes of Zapier and NetSuite run asynchronously. The NetSuite state entered contained a 'lock-record' action. Depending on which executed first Zapier may run into a locked record and then throws that HOIST message. It is resolved by excluding execution-contexts for the lock-record such that the zap can finish.
I also modified the workflow to have state transitions triggered by the Zap instead of being asynchronously executed by a saved search.

Hopefully it is helpful info for others with such error.


That’s an awesome news ​@Waldorf! We're really glad to hear the issue has been resolved. Thanks so much for sharing the solution—this will definitely be helpful for other Community members who might run into the same problem.

If you have any other questions, please don’t hesitate to reach out to the Community. We’re always happy to help! 🤗