elsa-workflows / elsa-workflows/elsa-core
Error outputs on activities
- Dominant language
- C#
- Stars
- 7.9k
- Forks
- 1.5k
- Avg merge
- 15h 22m
- Merged PRs (30d)
- 114
Description
Splitting #1100....
Designer application writer must be able to handle (at least some of the errors) that happen during workflow execution.
**This is a must for any serious workflow application.**
Currently it cannot because error outputs on activities are missing, they have just done or workflow fault.
One obvious example would be network glitch when using http request, I want to be able to know and try to retry if I wish so from within designer. Currently it would just fault the workflow. This one is actually a showstopper because you cannot workaround it in any way.....
- [ ] Redirect
- [ ] SendHttpRequest
- [ ] WriteHttpResponse
- [ ] SendEmail
- [ ] SaveToDropbox
- [ ] ClearTimer
- [ ] Cron
- [ ] StartAt
- [ ] Timer
- [ ] PublishRebusMessage
- [ ] SendRebusMessage
- [ ] BlobExists
- [ ] DeleteBlob
- [ ] ReadBlob
- [ ] WriteBlob
- [ ] DeleteFile
- [ ] EnumerateFiles
- [ ] FileExists
- [ ] OutFile
- [ ] ReadFile
- [ ] TempFile
Contributor guide
Assessment
This issue has not been assessed yet.