From 9610645315a08565dccd6d028f051a76efe68f02 Mon Sep 17 00:00:00 2001 From: Kerem Yilmaz Date: Tue, 17 Sep 2024 02:09:16 -0700 Subject: [PATCH] Add documentation for persist_browser_session (#836) --- docs/workflows/creating-workflows.mdx | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/workflows/creating-workflows.mdx b/docs/workflows/creating-workflows.mdx index b6a2871a..b2a8aadd 100644 --- a/docs/workflows/creating-workflows.mdx +++ b/docs/workflows/creating-workflows.mdx @@ -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