fix: Use `max()` instead of `min()` for `request_max_duration` statistic by vdusek · Pull Request #1701

fix: Use `max()` instead of `min()` for `request_max_duration` statistic by vdusek · Pull Request #1701 · apify/crawlee-python

The statistics tracking for maximum request duration was incorrectly
using min() instead of max(), causing the statistic to always show
the minimum duration instead of the maximum.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

self-assigned this

Jan 30, 2026

vdusek added t-tooling

Issues with this label are in the ownership of the tooling team.

adhoc

Ad-hoc unplanned task added during the sprint.

labels

Jan 30, 2026

Verify that request_max_duration correctly tracks the maximum duration
across multiple requests, ensuring it increases for longer requests
but doesn't decrease when shorter requests are recorded.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

vdusek deleted the fix/statistics-max-duration-logic branch

January 30, 2026 14:24

Mantisus pushed a commit to Mantisus/crawlee-python that referenced this pull request

Feb 9, 2026

…tic (apify#1701)

The statistics tracking for maximum request duration was incorrectly using `min()` instead of `max()`, causing the statistic to always show the minimum duration instead of the maximum.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>