Add documentation for persist_browser_session (#836)
This commit is contained in:
@@ -73,6 +73,12 @@ This is something the Skyvern team will need to set you up with today. If you're
|
||||
|
||||
Maps errors to specific error codes so you can have deterministic outputs
|
||||
|
||||
### `persist_browser_session`
|
||||
|
||||
The `persist_browser_session` flag indicates whether the browser session should be retained between different workflow runs. When enabled, it uses the same `user_data_dir` for each run and updates it at the end of each run. This is useful for maintaining the browser state, such as login sessions and cookies, across multiple runs of the same workflow, leading to more efficient and seamless execution.
|
||||
|
||||
> **Note:** This flag is set at the workflow level, not the block level, meaning it applies to the entire workflow's session persistence rather than individual blocks.
|
||||
|
||||
### `output_parameter_key` (autogenerated)
|
||||
|
||||
Specifies the output parameter of a specific block so it can be re-used in a subsequent block
|
||||
|
||||
Reference in New Issue
Block a user