Using a very basic script/flow to show the differences between these two runtime versions. The issue being that when the flow creates the job for my 7.2 script it doesn’t retain the named parameter provided by the flow. When it creates the job for my 5.1 script it keeps the named parameters correctly. I have a feeling it has something to do with Runbook itself. The flow is providing the same request, even the input for 7.2 looks correct but during execution (output) they become ‘wonky’.

Using a very basic script/flow to show the differences between these two runtime versions. The issue being that when the flow creates the job for my 7.2 script it doesn’t retain the named parameter provided by the flow. When it creates the job for my 5.1 script it keeps the named parameters correctly. I have a feeling it has something to do with Runbook itself. The flow is providing the same request, even the input for 7.2 looks correct but during execution (output) they become ‘wonky’.

Using a very basic script/flow to show the differences between these two runtime versions. The issue being that when the flow creates the job for my 7.2 script it doesn’t retain the named parameter provided by the flow. When it creates the job for my 5.1 script it keeps the named parameters correctly. I have a feeling it has something to do with Runbook itself. The flow is providing the same request, even the input for 7.2 looks correct but during execution (output) they become ‘wonky’.

Using a very basic script/flow to show the differences between these two runtime versions. The issue being that when the flow creates the job for my 7.2 script it doesn’t retain the named parameter provided by the flow. When it creates the job for my 5.1 script it keeps the named parameters correctly. I have a feeling it has something to do with Runbook itself. The flow is providing the same request, even the input for 7.2 looks correct but during execution (output) they become ‘wonky’.

Using a very basic script/flow to show the differences between these two runtime versions. The issue being that when the flow creates the job for my 7.2 script it doesn’t retain the named parameter provided by the flow. When it creates the job for my 5.1 script it keeps the named parameters correctly. I have a feeling it has something to do with Runbook itself. The flow is providing the same request, even the input for 7.2 looks correct but during execution (output) they become ‘wonky’.