409

Referenced by LIVE exchange contexts. A SOFT-DELETED context does not block the delete: its counterparty_type_id is cleared when it is deleted. The 'application/problem+json' body carries two RFC 9457 extension arrays, both NESTED under 'extensions' as this service publishes every extension member: 'extensions.referencingTenantIds' (UUIDs of tenants whose exchange contexts reference this type) and 'extensions.referencingContextIds' (UUIDs of the referencing exchange contexts themselves). Use them to issue concrete migration tickets to the affected tenants. Both arrays are CAPPED at 100 ids while the count in 'detail' is not, so for a type referenced by more than 100 contexts 'detail' names more than the arrays list. ONE CASE CARRIES NEITHER LIST: when a referencing context is committed between the pre-check and the delete, the database refuses, and the refusal reports what it knows -- that the delete was refused, and not by what. In that case 'extensions.referencingContextIds' is present and EMPTY and 'extensions.referencingTenantIds' is ABSENT, under the same omit-when-empty rule the tenant plane relies on; a client reading .length on the tenant array would fault on the one path this sentence describes. The refusal does not re-read to find out, because the violation surfaces at flush and leaves the transaction unable to answer another query. Retrying the DELETE re-runs the pre-check and returns both lists populated.