If this is on windows you can use the schtasks command to create a scheduled task that runs once, and then call it to start it during the execution of the job.
This will exit the commit phase with a success but will continue to run on the target afterwards. You'll have to use a different job to validate the success however, but you can do it with the schtasks command as well.
If it's on Unix, you'd have to use the post commands to call a script or command in the background with the nohup command so it's detached from BSA.
Thanks Found a different solution testing it, will yet you know the result of it
is the install 'hanging' and waiting for input or is it actually running for that long ? if it's actually running then i don't think backgrounding it is necessarily a good idea - how will you know of the install is a success ?
if it's hanging and waiting for input then you are not doing something w/ the silent install options or something like that.
Its not hanging it is waiting for cmd to close, result of the run is not bothered as it copied to different location.
So simple start cmd /c helped to close the job in console but it ran properly on the back ground without any issues
Oh ! Sorry I misread that part and didn't understand the issue... Yeah, you need to use cmd /c when calling things if you don't want the prompt to stay interactive and wait for input.