Not every slice is a date. dg.StaticPartitionsDefinition(["north", "south", "west"]) gives one partition per depot, region or customer tier: a fixed list you change in code.
When work is split by date and by another dimension, use dg.MultiPartitionsDefinition({"date": daily, "depot": depots}). Each partition is a pair, written as one key with the values joined by | in the alphabetical order of the dimension names: "2026-11-05|south" for date and depot. In code, context.partition_key.keys_by_dimension returns {"date": "2026-11-05", "depot": "south"}, which is safer than splitting the string.
A multi-partitioned asset can have at most one time dimension. Launching one partition from the terminal takes the joined key: --partition "2026-11-05|south". A key in the wrong order is simply a partition that does not exist.
Twenty-four partitions: eight days times three depots.