I have been tasked with creating a flowchart for tickets going through a process, with vertical swim lanes for the process stages and horizontal swim lanes for each resposible team as the work is kicked back and forth between them. The general structure of the flowchart is simple enough (almost completely linear with few decision points), however there are several additional states that any ticket can jump to from any point, concluding their flow through the process. A simple example of this would be that any point in the ticket could be cancelled, and this needs to be represented on the flowchart.
Now, I could display this with a decision ("is cancelled?") and resulting connector from every single process step (~25x) to each of these terminators (~5x), however adding in >100x additional elements and arrows to display this would create a lot of visual noise for what is a conceptually simple idea.
Is there either a best-practice or generally-accepted way of displaying this kind of relationship without cluttering up an otherwise simple flowchart?
