...
When saving to a file, in case of instance errors, the profiles could be “broken”. The profile folder should solve these problems - when you start the project, you launch run the instance and tell it to use a specific profile folder. During operation, the instance saves part of the data to the profile folder without your participation, as a regular browser does. And if the instance goes bad, the data will remain in the folder. Instance data such as:
...
| Note |
|---|
Unlike the profile-file, the profile-folder cannot be loaded using the “Operations on the profile” action. To use a profile-folder, at the beginning of the project you need to launch run an instance specifying the required profile-folder, and then the instance will be, as it were, “tied” to this profile-folder during operation. See examples below for details. |
...
+ you need to add a unique profile-folder name to it, just as you did in with the profile-file.
...
2. Run instance with an empty profile folder. Your instance will bind the profile folder to this path.
...
3. Load profile from file. Your profile-file will be loaded into the instance (which is already linked to the profile-folder)
...
4. Save the profile-folder. So the data from the instance will be saved to the profile folder (the ones that we downloaded from the file)
...
Prepare the path where the profile-folders will be stored. For example, in your project folder:
...
2. Run instance with an empty profile-folder. Your instance will bind the profile-folder to this path.
...
It is required to select “Chrome” and check mark the box “Use path to profile-folder”. There must be a checkbox “Create folder if it doesn’t exist”, otherwise the absence of necessary files in the folder will be interpreted as an error, and the red line will be exited.
3. Work up a profile. You perform Execute the actions that are necessary for feeding.
...
Set up a browserless project. In your project settings, mark that the project is browserless. This is necessary in order not to waste resources on launching running the default browser at the start of the project.
...
Please note that only one browser instance can be launched run in a specific profile folder at any given time. An attempt to launch run two (or more) instances in the same profile folder will result in an exit on the red branch.
...
Even if you close the browser using the Browser Settings => Run Instance => Without Browser action, ProjectMaker will still not release “let go” the profile folder. This is due to the peculiarities of the implementation of the instance within ProjectMaker.
To free up profile folder resources during debugging, you need to launch run the instance with a different type of browser, for example Firefox 45.
...