Troubleshooting Dust App Error in Hubspot Query Execution

Hi there! I hope you're all doing great 🙂 Quick question: I've replicated Clément FOLLIET - Welcome to the Jungle Dust App to query our Hubspot instance. It seem to be working (sometimes) and I get a response that is satisfactory. However, I often run into this error:

ERROR: Error running Dust app: failed to lookup address information: Name or service not known (code: dust_app_run_error)

Has anyone encountered this error before? If yes, can you please help me?

7 comments

David Ebbo
·
·
Feels like a DNS lookup issue. I assume the app is using a curl block? What's the hostname of the URL? Maybe it's a custom domain that's not fully propagated in DNS?
Luc Lagrange
·
·
Yes the app is using a curl/post blocks

Luc Lagrange

The URLs are specified in the agent configuration as follows:

Examples of API URLs:  
- Company details: api.hubapi.com/crm/v3/objects/companies/{companyId}  
- List of contacts: api.hubapi.com/crm/v3/objects/contacts  
- Deal details: api.hubapi.com/crm/v3/objects/deals/{dealId}  
- Contact search: api.hubapi.com/crm/v3/objects/contacts/search

David Ebbo
·
·
I would guess that one of the Dust backends failed a DNS lookup for some reason, and has negative caching till you hit the TTL. But it's odd that it would happen. Maybe Dust folks will have other thoughts here...
Luc Lagrange
·
·
Alright, thank you David Ebbo 😉
Luc Lagrange
·
·
Ok, found it 😉 In the test dataset, the url for the curl request is : api.hubapi.com/crm/v3/objects/companies/{{companyId}} However, I guess that when the agent tries to run the DustApp, the url can already include the https://, which was conflicting with the GET/POST blocks (see screenshot). My best guess is that the final url was : https://https://api.hubapi.com/crm/v3/objects/companies/{{companyId}} Which is not great. Adding the following instructions seem to have resolved the issue. When using an URL, NEVER include the https:// part of the url.
David Ebbo
·
·
Nice find! I missed the fact that your curl URL was not hard coded and was coming from the INPUT. Ideally, Dust would strip any protocol from the URL field before trying to pre-append its own (it does this, but only if you try to type it in). Note that you can see exactly how your app was called by the agent by going under Logs and choosing API.
🙌1