To homepage To homepage
Solved

Running Job execution not visible in Job Execution Log

Roy V
Rank
Userlevel 2

I’m in version 6590.1

I manually started a job. However when I look in the execution log from that job I don’t see an active running job.
If I look at the executions then I can see in that log that an execution is runnning.

What do I need to do to be able to see the current running job or is it a bug that running jobs are not visible? (then the status ‘Running’  which you can toggle does not make much sense in the ‘view execution log’  window).

greetings, Roy

icon

Best answer by Christian Hauggaard 10 May 2024, 14:48

View original

4 replies

rvgfox
Rank
Userlevel 4
Badge +1

I’ve detected that problem too, for me it’s a bug.

M
Rank

Same here, and also:

The execution log of my data sources tasks (sync/transfer/storage) is empty. While they are triggered every day in a ‘enable data on demand’ execution. Not sure if those logs are emtpy for you aswell?

rory.smith
Rank
Userlevel 6
Badge +7

Hi @Marcodenijs ,

on-demand loads do not have tasks for their load but can be found in the logging of the target table in DWH as ODX transfer steps and in the ODX Server as Outbound (transfer) of the OnDemand execution type. Essentially the ODX runs “on the fly” reloads of any ODX tables mapped to the items you execute in a DWH instance that have on-demand sources.

 

I agree that not being able to see a Job is running is very impractical. Especially if different types of activity require looking in different places.

Christian Hauggaard
Rank
Userlevel 6
Badge +5

@Roy V can you see the the job with execution state “running” in the Job monitor? 

 

I have been able to reproduce the issue you describe regarding the Running filter/toggle in the job execution log and have passed this onto the product team, please check upcoming release notes for a fix.

Reply


Terms and ConditionsCookie settings