Daniel Gerlag

There is currently no built in way to do this, but you could catch the exceptions inside your steps and output results that the workflow can make decisions on.

@gonengf you'd need to implement the core logic in [ExecutionResultProcessor](https://github.com/danielgerlag/workflow-core/blob/master/src/WorkflowCore/Services/ExecutionResultProcessor.cs) And then extend the [OnError fluent method](https://github.com/danielgerlag/workflow-core/blob/master/src/WorkflowCore/Services/FluentBuilders/StepBuilder.cs#L188) to take exception types as an optional parameter. Also, would need to add...

I think we'd want some kind of policy object where you could chain multiple behaviors together, rather than a static single fallback. Something like the way this library works -...

That would be great, you would need to implement the `IQueueProvider` interface... You can look at the RabbitMQ implementation as an example - https://github.com/danielgerlag/workflow-core/tree/master/src/providers/WorkflowCore.QueueProviders.RabbitMQ

You can configure a step to have retry behavior - https://workflow-core.readthedocs.io/en/latest/error-handling/

Should you be terminating the workflow if you intend to retry it later?

You can set the default error behavior per workflow. ```c# public void Build(IWorkflowBuilder builder) { builder .UseDefaultErrorBehavior(WorkflowErrorHandling.Suspend) .StartWith() .Then(); } ``` or per step ```c# public void Build(IWorkflowBuilder builder) {...

The in memory persistence provider is only meant for testing.

https://workflow-core.readthedocs.io/en/latest/control-structures/#json-yaml-api_3

Are you running multiple nodes?