What Causes the PipedreamError and How to Obtain Better Debugging Information?

Help
1

This topic was automatically generated from Slack. You can find the original thread here.

Hi team, I got a PipedreamError with the following details - I have a feeling this is related to using the method rawAccessToken() due to the stack involving oauthTokens, but can someone help confirm what might have gone wrong? Is it possible to get better debugging info in the error message as well? We see this problem about every couple of weeks or so

"type": "PipedreamError",
"message": "Unable to connect. Is the computer able to access the url?",
"stack": "Error: Unable to connect. Is the computer able to access the url?
    at <anonymous> (/app/node_modules/@pipedream/sdk/dist/esm/api/resources/oauthTokens/client/Client.mjs:86:38)
    at fulfilled (/app/node_modules/@pipedream/sdk/dist/esm/api/resources/oauthTokens/client/Client.mjs:5:58)
    at processTicksAndRejections (native:7:39)",
"rawResponse": {
"headers": { 0 },
"redirected": false,
"status": 0,
"statusText": "Unknown Error",
"type": "error",
"url": ""
}
What Might Have Caused the PipedreamError Related to rawAccessToken() Method and How Can Better Debugging Info be Obtained?
2

bump can i get help with this?

3

Sorry, what are you trying to do / when are you getting this error? Can you provide some more context?

4

Hi Danny, we are trying to get the access token to connect to the client and list tools. We have a plan to add retries but we also want to know if the root cause is internal to Pipedream / can be fixed because we see this issue every couple of weeks. Thanks!

5

I have no idea what your implementation looks like, but the core method in the SDK is working fine:

import { PipedreamClient } from "@pipedream/sdk";
 
const client = new PipedreamClient({
  projectEnvironment: PIPEDREAM_ENVIRONMENT,
  clientId: PIPEDREAM_CLIENT_ID,
  clientSecret: PIPEDREAM_CLIENT_SECRET,
  projectId: PIPEDREAM_PROJECT_ID
});
 
const accessToken = await client.rawAccessToken;
 
console.log(accessToken);
6

This error is from your LLM, not Pipedream:

"message": "Unable to connect. Is the computer able to access the url?",
"stack": "Error: Unable to connect. Is the computer able to access the url?
7

One thing that may help narrow this down is separating token acquisition failures from downstream tool-list calls.

If the stack is dying inside the OAuth token client before you even get a usable token back, I’d log three things around the exact failure window:

1. Whether the same credentials work immediately on retry
2. Whether the failure lines up with any short-lived network egress issue from your runtime
3. Whether the raw token request is failing on DNS / connect / timeout versus getting an actual HTTP response

The clue in your raw response is that status is `0` with an empty URL, which usually feels more like a network-layer failure than a normal OAuth application error. If retries consistently fix it, I’d treat it like an intermittent transport issue first and then add request-level timing / connectivity logs around the token exchange path.