I have an organizational/best practice question. In my main file there is 1 state machine.
In the state machine scope I have some variables (These are mostly constants that don’t change throughout the entire process.)
Then I have some in/out arguments. All my arguments in my state machine scope are in/out because the state machine has become somewhat of a controller, passing arguments into workflows and getting results out of them to be passed into others.
Long story short, I got an error on Orchestrator because I have an in/out argument of the type DataTable that is too big to be an output of the process. I can clear the datatable variable at the end of the state machine to fix this problem, but then I still have output arguments at the end of the state machine that I do not need.
Am I organizing my arguments wrong? I don’t need to have any output arguments to pass after the process is completed, but I thought I needed them to be in/out to pass them into other workflows during the state machine process.
Should I make my ioArguments variables instead if I don’t need to pass them out of the state machine?
Let me know.