AnsweredAssumed Answered

jobs set to immediate show up as scheduled

Question asked by beekerc2 on May 27, 2010
Latest reply on Jun 2, 2014 by Jerin_Sebastian
Has anyone run into this situation?
I submit a job to run immediately, but when i go to the Logs sub tab i don't see it.
I check back on the Schedule Jobs sub tab and see it in a Scheduled status.
However, there are no jobs in Processing state, so it's not an incompatible jobs issue.
I've seen launch delays of a minute or two, but once it gets to be 5 minutes or more, it's a certainty it will never launch.
I've had such jobs stuck in the scheduled state for 72 hours before i cancel and delete them.
I've also stopped and started the bg service, which runs jobs and processes.
I have two other Clarity environments which have identical code bases and NSA configurations and those two launch jobs perfectly every time.
Can anyone share insight as to where i should start looking beyond the usual troubleshooting suspects?