Results
3
comments of
kkhnifes
What's the status on this?
I think this is expected behavior of graphql mutations. It should run the mutation with both params but the responses overwrite each other (first come first serve)