While you can undo any run, one of the main use case is for processes with carry-over enabled. A file with bad data may get submitted by mistake or unintentionally (e.g. through automatic submission) and trigger a run in Duco. This could result in many incorrect matches and new unwanted exceptions that may be mixed up with legitimate exceptions carried-over from previous run. You can now mark the run as failed. Duco will then close all the new exceptions created, re-open exceptions from previous successful run, and restore their workflow statuses.
Articles in this section
- Can you automate the Excel results download?
- Can you submit one side automatically via SFTP/API and the other through manual upload?
- How does Duco identify the “new occurrence” of a previously manually force closed item?
- What is the limit of the carry over period?
- What is the maximum length of a Comment on an exception?
- What is the preferred way to “clear” out old exceptions on a process in bulk?
- When multiple files are uploaded within a zip file, is there any way to identify which sub file within the zip file a particular record comes from?
- Which formats can be extracted via the API?
- Why do duplicate records appear in the excluded section of my run overview?
- Why is there a "Mark as failed" option?