We're seeing an issue where jobs becomes inaccessible via the TAC Job Conductor. We've traced the issue to the backend DB and a huge amount of "InstantRunTriggers" being created for a specific job. This in turn causes a "500" error in the TAC as it tries to gather job information before rendering the page. The result is the TAC will never display data on the job in question.
Our solution involves identifying the job causing the problem; shutting down the TAC to stop the trigger generation; then manually clearing literally thousands of "InstantRunTrigger" entries from various Quartz tables for a single job.
Has anyone else seen this behavior?
