This is to avoid creating spurious runs in run storage.
- Group Reviewers
- R1:2073981febbd: Use executePlan within dagster-graphql-mediated execution engines
this is great.
Please add some manual testing within dagit to your test plan as this is the pretty significant change. It's a bit tedious but I think exercising the pipelines in our examples repo would be appropriate here.
This is a pre-existing issue, but it seems like this type of processing is pretty unnecessary and we should just have a generic codepath for all error types. Meaning that in the error case we could pass along a message, a type, and the graphql payload, and there would be no required specialization per-type at this layer.