When should teams use Diagrid for Dapr state stores?

Dapr state stores become more sensitive as more services depend on them for workflow progress, user context, or application state. Teams should consider Diagrid when they want production support and operational consistency around Dapr state APIs rather than managing every integration detail themselves. Important review areas include state consistency expectations, retry behavior, component configuration, and visibility into failures. Catalyst can matter when state is tied to durable workflows or agent execution. The decision should reflect how costly state mistakes would be in the live system.