For example, I’d split this into at least two separate programs:

Warm-up tool: runs the preparation logic and saves the profiles and their data.
Main tool: loads that saved data and does the actual work.

@sergerdn Unfortunately I have quite literally done this exact approach, but it is not as simple of a solution as this, and it still is not working.

Fair enough.

BAS lets people build large projects without much programming experience. That’s where things like KISS, SOLID, separating responsibilities, and documenting how everything works can get overlooked. Eventually, even a small change becomes hard to make without breaking something else.

For example, I’d split this into at least two separate programs:

• Warm-up tool: runs the preparation logic and saves the profiles and their data.
• Main tool: loads that saved data and does the actual work.

Each has its own job, and you can test them separately. That makes it easier to narrow down where things go wrong.

If everything is mixed into one huge BAS script and nothing is documented, someone first has to work out what it does, how the pieces depend on each other, and what a change might break. At that point, “fix my bot” can turn into reverse-engineering the whole project before you can even start fixing it.

I haven’t seen your project, so I don’t know if this applies to yours. I’m just talking about how BAS projects often end up being put together — one big mess, lol.

why my bot is being detected, and make it work properly.

I've posted this general approach on the forum plenty of times, but here we go again.

Easy fix. Just two parts. 🙂

The same general approach applies to Google and other websites, though the details need to be tested for each site.

Technical side

• The right proxies for the site you're working with, including QUIC support where needed. Mobile proxies are much better in my exiprience.
• Your own fingerprints — collect them yourself and filter them. BAS has tools for that.

Non-technical side

Have a plan for how you prepare and use your digital identities:

• Give new browser profiles time to warm up — say, 30 days as an example.
• Keep maintaining them after that.
• Decide when a profile is ready and what you'll use it for: watching a video, clicking something, leaving a comment, etc.

So yeah, “easy” — just build and maintain a whole system around your bot.