This topic was automatically generated from Slack. You can find the original thread here.
Hey all, I am very randomly getting this from our PIpedream SDK:
An error occurred while calling the tool: Error: Status code: 401\nBody: {\n "error": "Unauthorized"\n
Nothing has changed on our code, and this was working previously. I notice that if I comment out the x-pd-environment, then I get a link to sign in.
Is there a bug or anything I should be aware of on your side?
To be clear, this is happening with a code snippet nearly identical to this one
cc I am a bit blocked on this and see that you are online. Would you be able to help by chance?
cc in case pi has any ideas too
I’m sorry you’re running into this issue and that it’s blocking your work. A 401 “Unauthorized” error from the Pipedream SDK typically means that the authentication credentials being sent are invalid, expired, or missing. Since you mentioned that nothing has changed in your code, but commenting out the x-pd-environment header gives you a sign-in link, here are some things to check: ### Troubleshooting Steps 1. Check API Keys / Tokens - Make sure your API key or token is still valid and hasn’t been revoked or expired. - If your credentials are stored in environment variables or a secrets manager, verify they haven’t changed. 2. x-pd-environment Header - The x-pd-environment header is used to specify the Pipedream environment (like “production” or “development”). If this value is incorrect or references an environment you no longer have access to, you may get a 401 error. - Try removing or updating this header to see if authentication works without it, or double-check that the environment exists and you have access. 3. Session Expiry / Re-authentication - If you’re using OAuth or a session-based authentication, your session may have expired and you need to re-authenticate. 4. Recent Changes on Pipedream’s Side - While you said nothing changed on your end, it’s possible there was a change on Pipedream’s side affecting authentication. Check Pipedream status or changelog for any relevant updates. 5. SDK Version - If you recently updated the Pipedream SDK, make sure you’re using a compatible version. Sometimes breaking changes are introduced in new versions. ### Next Steps - Try authenticating again or generating a new API key/token. - Test your request without the x-pd-environment header. - If you continue to see the issue, please reach out to Support - Pipedream for more direct help from the Pipedream team. Again, sorry for the trouble—let me know if you need more help or have more details to share!
Hi , thank you for reaching out.
The Pipedream team has aware of this issue and is working on a fix, will grt back to you soon
Hi , the Pipedream team has made some updates, would you mind try again to see if the issue is fixed?
It works now! could you update [status.pipedream.com](http://status.pipedream.com)? I spent four hours trying to figure out if it was something on our side
Thank you for your information.
I’ll inform Pipedream team if the status page needs to be updated.
Thank you for checking on your side first, in the future you can ping us on Slack so we can help you faster 