[Bug]: Default behaviour timeout not set if no timeout provided

Open
#3,748 0 comments 0 reactions 1 assignee View on GitHub

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

bug
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
  1. Create a workflow.
  2. 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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from webrecorder/browsertrix

All issues in webrecorder/browsertrix

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.