UpdateForecastScenarioOrderMutation

Replace the household's scenario order with the supplied list.

Concurrency: no optimistic version field — matches the convention used by every other reorder mutation in this schema (UpdateAccountOrderMutation, UpdateCategoryGroupOrderMutation, etc.).

A client whose list is stale because a sibling added or removed a scenario gets Scenario list does not match active scenarios and should refetch. Two concurrent reorders against the *same* set are "last write wins" — same semantics as every drag-reorder mutation in this codebase. Revisit if endpoint needs versioning.

type UpdateForecastScenarioOrderMutation {
  errors: PayloadError
  scenarios: [ForecastScenarioListItemType!]
}

Fields

UpdateForecastScenarioOrderMutation.errors ● PayloadError object

UpdateForecastScenarioOrderMutation.scenarios ● [ForecastScenarioListItemType!] list object

Returned By

updateForecastScenarioOrder mutation