Adding known limitations

docs-v2/pages/connect/troubleshooting.mdx

@@ -1,22 +1,24 @@
+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).
 
 ### Error connecting an account
 
 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.
+The user may have closed the OAuth popup window without completing authorization.
+
+<Callout type="info">
+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.
+</Callout>

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).
+- 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).