It may be possible in som very cumbersome way, but I would try to avoid this way of running things
If the procedure is triggered from some environment , like for example VC, then the next VC job should be triggered by this environment after the completion of the proc. So everything i triggered from the same place. Then you avoid having jobs that trigger jobs that trigger jobs and so on.
Is this procedure scheduled to run on time on the database itself maybe? You could have the procedure write to some LogTable you create, and then have a VC trigger that looks for this entry.
Thomas