diff --git a/docs-v2/pages/connect/troubleshooting.mdx b/docs-v2/pages/connect/troubleshooting.mdx index a0d63c2dbbbcc..2c3791f450075 100644 --- a/docs-v2/pages/connect/troubleshooting.mdx +++ b/docs-v2/pages/connect/troubleshooting.mdx @@ -1,10 +1,12 @@ +import Callout from '@/components/Callout' + # Troubleshooting Below are some common errors when connecting your users' accounts via Pipedream Connect. ### Error creating a Connect token -_Error creating token: Error: Failed to obtain OAuth token: Response Error: 401 Unauthorized_ +>Error creating token: Error: Failed to obtain OAuth token: Response Error: 401 Unauthorized Authorization to the Pipedream API failed when creating the Connect token. Double-check the client ID or secret for your [Pipedream OAuth client](/connect/api#authentication). @@ -12,11 +14,11 @@ Authorization to the Pipedream API failed when creating the Connect token. Doubl Most errors when connecting an account are related to the [Connect token](/connect/tokens), which Pipedream validates from the Connect iFrame. -#### Possible errors +#### Common errors -_This link has expired. Please request a new one from the app developer._ +>This link has expired. Please request a new one from the app developer. -_This session has expired. Please refresh the page to try again._ +>This session has expired. Please refresh the page to try again. #### Troubleshooting steps @@ -32,14 +34,18 @@ and check the response for error messages. #### Token validation errors -_The Pipedream Connect token is invalid. Please generate a new one and try again._ +>The Pipedream Connect token is invalid. Please generate a new one and try again. Connect tokens expire, and are only able to be used once. Try generating a new token and try again. -_App not found. Please check your app id._ +>App not found. Please check your app id. Double-check the app slug you're passing [when connecting your user's account](/connect/quickstart#connect-your-users-account). ### Connection failed. Please retry or contact support. -The user may have closed the OAuth popup window without completing authorization. \ No newline at end of file +The user may have closed the OAuth popup window without completing authorization. + + +If you're still have trouble or hitting an error that isn't listed here, [get in touch with us](https://pipedream.com/support). We'd love to help. + \ No newline at end of file diff --git a/docs-v2/pages/connect/workflows.mdx b/docs-v2/pages/connect/workflows.mdx index a6574b69bc22b..f54a27280f200 100644 --- a/docs-v2/pages/connect/workflows.mdx +++ b/docs-v2/pages/connect/workflows.mdx @@ -277,6 +277,7 @@ curl -X POST https://{your-endpoint-url} \ Pipedream Connect Error: Required account for hubspot not found for external user ID abc-123 in development ``` + ### Common errors #### No external user ID passed, but one or more steps require it - One or more steps in the workflow are configured to **Use end user's auth via Connect**, but no external user ID was passed when invoking the workflow. @@ -292,4 +293,18 @@ Pipedream Connect Error: Required account for hubspot not found for external use #### Running workflows for your users in production requires a higher tier plan - Anyone is able to run workflows for your end users in `development`. The Business plan is required to run on behalf of `production` users. -- Schedule a call with our sales team and learn more about pricing [here](https://pipedream.com/pricing?plan=Enterprise). \ No newline at end of file +- Schedule a call with our sales team and learn more about pricing [here](https://pipedream.com/pricing?plan=Enterprise). + +## Known limitations + +#### Using your end user's auth is not currently supported within control flow segments +- Currently, you can only use your end user's auth in the linear execution paths of a Pipedream workflow. +- You can still use control flow features in your Connect-enabled workflow, but the step(s) that use an end user's auth must be in the linear [execution path](/workflows/control-flow#execution-path) of the workflow. + +#### Workflows can only use a single external user's auth per execution +- Right now you cannot invoke a workflow to loop through many external user IDs within a single execution. +- You can only run a workflow for a single external user ID at a time (for now). + +#### The external user ID to use during execution must be passed in the triggering event +- You can't run a workflow on a timer for example, and look up the external user ID to use at runtime. +- The external user ID must be passed in the triggering event, typically via [HTTP trigger](#invoke-the-workflow). \ No newline at end of file diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml index b3349d11d314b..d707867e4e87a 100644 --- a/pnpm-lock.yaml +++ b/pnpm-lock.yaml @@ -1499,8 +1499,7 @@ importers: components/call_fire: {} - components/callerapi: - specifiers: {} + components/callerapi: {} components/callhub: dependencies: @@ -24516,22 +24515,22 @@ packages: superagent@3.8.1: resolution: {integrity: sha512-VMBFLYgFuRdfeNQSMLbxGSLfmXL/xc+OO+BZp41Za/NRDBet/BNbkRJrYzCUu0u4GU0i/ml2dtT8b9qgkw9z6Q==} engines: {node: '>= 4.0'} - deprecated: Please upgrade to v7.0.2+ of superagent. We have fixed numerous issues with streams, form-data, attach(), filesystem errors not bubbling up (ENOENT on attach()), and all tests are now passing. See the releases tab for more information at . + deprecated: Please upgrade to v9.0.0+ as we have fixed a public vulnerability with formidable dependency. Note that v9.0.0+ requires Node.js v14.18.0+. See https://github.com/ladjs/superagent/pull/1800 for insight. This project is supported and maintained by the team at Forward Email @ https://forwardemail.net superagent@4.1.0: resolution: {integrity: sha512-FT3QLMasz0YyCd4uIi5HNe+3t/onxMyEho7C3PSqmti3Twgy2rXT4fmkTz6wRL6bTF4uzPcfkUCa8u4JWHw8Ag==} engines: {node: '>= 6.0'} - deprecated: Please upgrade to v7.0.2+ of superagent. We have fixed numerous issues with streams, form-data, attach(), filesystem errors not bubbling up (ENOENT on attach()), and all tests are now passing. See the releases tab for more information at . + deprecated: Please upgrade to v9.0.0+ as we have fixed a public vulnerability with formidable dependency. Note that v9.0.0+ requires Node.js v14.18.0+. See https://github.com/ladjs/superagent/pull/1800 for insight. This project is supported and maintained by the team at Forward Email @ https://forwardemail.net superagent@5.3.1: resolution: {integrity: sha512-wjJ/MoTid2/RuGCOFtlacyGNxN9QLMgcpYLDQlWFIhhdJ93kNscFonGvrpAHSCVjRVj++DGCglocF7Aej1KHvQ==} engines: {node: '>= 7.0.0'} - deprecated: Please upgrade to v7.0.2+ of superagent. We have fixed numerous issues with streams, form-data, attach(), filesystem errors not bubbling up (ENOENT on attach()), and all tests are now passing. See the releases tab for more information at . + deprecated: Please upgrade to v9.0.0+ as we have fixed a public vulnerability with formidable dependency. Note that v9.0.0+ requires Node.js v14.18.0+. See https://github.com/ladjs/superagent/pull/1800 for insight. This project is supported and maintained by the team at Forward Email @ https://forwardemail.net superagent@7.1.6: resolution: {integrity: sha512-gZkVCQR1gy/oUXr+kxJMLDjla434KmSOKbx5iGD30Ql+AkJQ/YlPKECJy2nhqOsHLjGHzoDTXNSjhnvWhzKk7g==} engines: {node: '>=6.4.0 <13 || >=14'} - deprecated: Please downgrade to v7.1.5 if you need IE/ActiveXObject support OR upgrade to v8.0.0 as we no longer support IE and published an incorrect patch version (see https://github.com/visionmedia/superagent/issues/1731) + deprecated: Please upgrade to v9.0.0+ as we have fixed a public vulnerability with formidable dependency. Note that v9.0.0+ requires Node.js v14.18.0+. See https://github.com/ladjs/superagent/pull/1800 for insight. This project is supported and maintained by the team at Forward Email @ https://forwardemail.net supports-color@2.0.0: resolution: {integrity: sha512-KKNVtd6pCYgPIKU4cp2733HWYCpplQhddZLBUryaAHou723x+FRzQ5Df824Fj+IyyuiQTRoub4SnIFfIcrp70g==}