Azure Cosmos cannot serve a multi-field ORDER BY without a matching composite index (the local emulator is lenient, real Cosmos returns HTTP 400). The fleet listJobs() query orders by (priorityOrder, createdAt), which broke GET /api/fleet/metrics and /api/fleet/jobs on real Cosmos. - ContainerConfig gains an optional `compositeIndexes` field - container init applies it on create AND reconciles it onto existing containers (createIfNotExists never updates an existing index policy) - fleet_jobs declares the (priorityOrder ASC, createdAt ASC) composite index Verified live against Azure Cosmos: both endpoints now return 200. Generated with [Devin](https://cli.devin.ai/docs) Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| cowork-service | ||
| extraction-service | ||
| mcp-server | ||
| monitoring | ||
| platform-service | ||