Is it possible to dynamically assign keys to mutation instances in TanStack Query?

[rudzky]

I’m working on a scenario where I need to send multiple requests using a single mutation (useMutation). Each request should have a unique key (e.g., a custom identifier) to:

Track the state of individual requests (loading, success, error) independently.
Optionally cancel or manage specific requests programmatically.
Currently, useMutation does not seem to provide a built-in way to dynamically assign or associate custom keys with individual mutation instances. Is there a recommended way to handle such use cases?

If not directly supported, are there any best practices or patterns for managing dynamic mutation instances tied to unique identifiers?

Thanks for your insights, and I appreciate the amazing work you’re doing with TanStack Query!

[TkDodo]

you can useMutationState to get the state of related mutations. It’s easier if they have the same key then, and you can additionally filter by variables.