Are there

retry

semantics in Dagster? I can't find anything in the docs referencing that. Is it down to the author of the solid to code that?

no retry semantics yet, but it’s definitely something we’re thinking about. Most likely will add solid level configuration for this, although I could imagine a decorator-based version making sense as well. For now, yes you’ll have to add your own retry logic around solid execution within the body of your solid compute function

Thanks Nate! I think a decorator-based implementation would be quite elegant and would maintain the separation of concerns. Perhaps we'll give that a go