Is there a way in the request pipeline to skip the write and return a custom response? I see that I can technically return a value in the error message but I was wondering if there was a more efficient way

@aurnik https://www.graph.cool/docs/reference/functions/error-handling-quawa7aed0/#returning-error-objects

Right, I was more wondering if a response could be returned that wasn't inside the error object. I'm trying to return an actual response from a separate query made inside the pipeline, to be used with nested mutations. Still tackling upsert with nested mutations where the nested part will either move forward with the pipeline if it doesnt already exist but if it does, it will skip the write step and return the existing id to the mutation

Well, you know if the nested part already exists on the client, because it has an ID right?

Right now the nested part does not always have an ID even if it exists, however it does have a different unique field

That doesn't help (yet)

So I guess now the problem is that I believe currently you can't connect a relation with any unique field other than ID

No, I created the FR for that...

Just upvoted it 👍