Cron error: 413 Request Too Long when pushing signals

I’m seeing recurring CrowdSec errors during cron.

Environment:

* Drupal core: 11.3.10
* PHP: 8.4.21
* drupal/crowdsec: 1.2.5
* crowdsec/remediation-engine: 4.3.2
* Database: MySQL

Error:

CrowdSec\CapiClient\ClientException: Error during request: Unexpected response status code: 413. Body was: {“message”: “Request Too Long”} in CrowdSec\CapiClient\Watcher->manageRequest() line 580 of vendor/crowdsec/capi-client/src/Watcher.php.

Relevant backtrace:

modules/contrib/crowdsec/src/Buffer.php(309): CrowdSec\CapiClient\Watcher->pushSignals(Array)
modules/contrib/crowdsec/src/Hook/CrowdsecHooks.php(50): Drupal\crowdsec\Buffer->push()
core/lib/Drupal/Core/Cron.php(275): Drupal\crowdsec\Hook\CrowdsecHooks->cron()

I also see repeated watchdog messages like:

Buffered signal to drupal/4xx-scan for [IP address]

The Drupal crowdsec queue is empty, so this seems to be stored in the module’s own buffer.

Questions:

* Is there a safe way to flush only the CrowdSec signal buffer?
* Should the module split large signal batches to avoid 413 responses?
* Is there a setting to limit the number of signals sent during cron?

Thanks.