Forum Discussion
Mike1613
2 years agoNew Contributor III
Quick update on this topic, we identified some 'corrupt' data that is causing an error when the workflow throws this message in the error log (shown below). When this occurs, the execution of the workflow impacted dramatically slows down with no other messages that have been identified. We are evaluating options to see if we can identify the 'corrupted' data outside of clearing everything and rebuilding (ideally worse case since we are in a production application). More to come...
Related Content
- 10 months ago
- 12 months ago
- 8 months ago
- 3 years ago
- 6 months ago