[Bug]: Default behaviour timeout not set if no timeout provided
Maintainers usually reply within 1 day
@mistydemeo is already working on this.
Since Oct 20, 2026.
Assessment
This issue has not been assessed yet.
Description
Browsertrix Version
v1.26.1-21bd6c6
Browsertrix Host
Hosted by Webrecorder
What did you expect to happen? What happened instead?
If the user leaves the behaviour timeout field at its default, we serialize no value into the config and end up passing no value to the crawler. As a result the crawler picks its own default value. Since the crawler's default is 90 seconds, but the user interface's default is 300, we end up seeing behaviours timing out at 90 seconds instead of the 300 seconds users expect.
Reproduction instructions
- Create a workflow.
- Enter no value in the behaviour timeout
Expected behaviour:
Behaviours time out after 300 seconds.
Actual behaviour:
Behaviours time out after 90 seconds.
Screenshots / Video
No response
Environment
No response
Additional details
No response
- Dominant language
- TypeScript
- Stars
- 502
- Forks
- 83
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 32
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from webrecorder/browsertrix
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
webrecorder/browsertrix#3823 ·
Maintainers usually reply within 1 day
-
[Bug]: DigitalOcean ansible playbook deploys masked MongoDB password (********) with doctl >= 2.0.0Possibly taken @axllent claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
webrecorder/browsertrix#3815 · 2 comments ·
Maintainers usually reply within 1 day
-
enhancement idea
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
webrecorder/browsertrix#3715 ·
Maintainers usually reply within 1 day
-
bug front end
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
webrecorder/browsertrix#3708 ·
Maintainers usually reply within 1 day
-
back end
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
webrecorder/browsertrix#3626 ·
Maintainers usually reply within 1 day
All issues in webrecorder/browsertrix
Similar issues
-
bug documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Potential Bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Comfy-Org/ComfyUI_frontend#23773 ·
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 85/100
lingdojo/kana-dojo#34301 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
github/gh-aw-firewall#11797 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
code-yeongyu/senpi#7007 ·
Maintainers usually reply within 1 day