Provide a clear and concise description of what you want to happen.
Enforce a maximum of 12 maps per batch map operation to protect server performance.
- Add validation on batch map creation (UI + server) to cap at 12 maps
- Display clear error/message to user (UI) when limit is exceeded
- Applies to both one-off batch jobs, scheduled TBD
Is there anything else you can add about the proposal? You might want to link to related issues here, if you haven't already.
WMS server can handle ~17–30 req/s depending on config, but concurrent batch operations with too many maps risk overloading the tile server. Team agreed on 12 as the safe ceiling during 4/30 dev sync.
Provide a clear and concise description of what you want to happen.
Enforce a maximum of 12 maps per batch map operation to protect server performance.
Is there anything else you can add about the proposal? You might want to link to related issues here, if you haven't already.
WMS server can handle ~17–30 req/s depending on config, but concurrent batch operations with too many maps risk overloading the tile server. Team agreed on 12 as the safe ceiling during 4/30 dev sync.