Skip to content

Commit 663754a

Browse files
Removing caveat about subflows in connect workflows
1 parent 95b8792 commit 663754a

File tree

2 files changed

+2
-4
lines changed

2 files changed

+2
-4
lines changed

docs-v2/pages/connect/workflows.mdx

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -297,10 +297,6 @@ Pipedream Connect Error: Required account for hubspot not found for external use
297297
298298
## Known limitations
299299
300-
#### Using your end user's auth is not currently supported within control flow segments
301-
- Currently, you can only use your end user's auth in the linear execution paths of a Pipedream workflow.
302-
- 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.
303-
304300
#### Workflows can only use a single external user's auth per execution
305301
- Right now you cannot invoke a workflow to loop through many external user IDs within a single execution.
306302
- You can only run a workflow for a single external user ID at a time (for now).

pnpm-lock.yaml

Lines changed: 2 additions & 0 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

0 commit comments

Comments
 (0)