Bug 226 - Scheduler - Separate Session Hung Session

Cory Fifield -

Resolved in Version


Bug: When a scheduled job is kicked off using the service with separate session enabled, that job will run and complete but will not close. Can lead to multiple sessions open.


Steps to reproduce:

  1. Open/Create a job that uses separate session.
  2. Schedule the job and run it through the service.


Expected Result: Job runs and separate session closes.

Actual Result: Job runs and the session just remains open.

Have more questions? Submit a request