- Type is fixed per group:
simulationtraining
- Each group has one
group_id - Each line item is tracked independently (
partial acceptis supported)
Why Use Groups
- Submit many items in one flow (up to configured max per group)
- Track aggregate progress with one ID
- Inspect per-item errors without losing successful items
- Cancel remaining queued/running work at group level
API Endpoints
POST /v1/submission-groupsPOST /v1/submission-groups/{group_id}/ingestGET /v1/submission-groups/{group_id}GET /v1/submission-groupsGET /v1/submission-groups/{group_id}/itemsGET /v1/submission-groups/{group_id}/eventsPOST /v1/submission-groups/{group_id}/cancel
SDK Shortcuts
client.submit_many_jobs(...)client.submit_many_training_runs(...)client.watch_submission_group(group_id, ...)client.list_submission_group_items(group_id, ...)client.cancel_submission_group(group_id)
Example: Batch Simulation Submit
Monitor From Terminal
Item-Level Debugging
Filter Existing Workloads By Group
GET /v0/jobs?submission_group_id=<group_id>GET /v1/training-runs?submission_group_id=<group_id>