Skip to content

Conversation

@ikreymer
Copy link
Member

profile crawlerChannel default:

  • use crawlerChannel from profile when launching browser for profile

profile proxyId constraint: (backend part of #2982)

  • ensure workflow proxyId set to that profile.proxyId when creating or updating workflow
  • also ensure correct proxyId from profile is used when starting crawls

- use crawlerChannel from profile when launching browser for profile

profile proxyId constraint: (backend part of #2982)
- ensure workflow proxyId set to that profile.proxyId, if using profile, when creating, updating workflow
- also ensure correct proxyId (from profile) is used when starting crawls
@ikreymer ikreymer requested a review from tw4l November 14, 2025 07:42
Copy link
Member

@tw4l tw4l left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the change!

@ikreymer ikreymer merged commit 4314e2a into main Nov 18, 2025
25 of 26 checks passed
@ikreymer ikreymer deleted the profile-constraints-fix branch November 18, 2025 18:13
ikreymer added a commit that referenced this pull request Nov 21, 2025
- follow-up to #2988, alternative to #3008
- clear proxyId in workflow if using profile, ensure it is always empty for new workflows/updated workflows that have a profile
- add migration to clear proxyId if profileid is set for existing workflows
- avoids having to update proxyId in workflows when it changes in the profile
- fix assertion when updating proxy to return 400 if proxy is invalid
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants