Horizontal worker dyno scaling in Scalingo v2.0 lacks auto-scaling thresholds

Goal

Determine whether Scalingo v2.0 supports configurable auto-scaling triggers for worker dynos, or whether horizontal scaling remains a manual-only operation.

Constraints and uncertainty

Documentation for the v2.0 release describes horizontal scaling through a manual scaling command and limits it to worker dynos, excluding web dynos. Scaling configuration lives in the app settings and can be overridden by an environment variable, while the scaling API returns current dyno counts without exposing auto-scaling policies. Region-specific caps may apply, and CLI output may be delayed by caching.

Because no auto-scaling thresholds are documented, it is unclear whether users can define CPU, memory, or request-based rules, or whether they must invoke scaling manually for each adjustment.

Questions

• Can auto-scaling thresholds be configured for worker dynos in Scalingo v2.0?
• Is manual invocation the only supported scaling path as of v2.0?
• Does the scaling API expose pending auto-scaling policies or only current dyno counts?