Skip to main content
To homepage To homepage
Solved

Running Job execution not visible in Job Execution Log

Roy V
Problem Solver
Forum|alt.badge.img+2
  • Roy V
  • Problem Solver
  • 56 replies

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

Best answer by Christian Hauggaard

@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.

View original
    Did this topic help you find an answer to your question?

    6 replies

    rvgfox
    Problem Solver
    Forum|alt.badge.img+4
    • rvgfox
    • Problem Solver
    • 222 replies
    • May 7, 2024

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

    M
    Contributor
    • Marcodenijs
    • Contributor
    • 10 replies
    • May 7, 2024

    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
    TimeXtender Xpert
    Forum|alt.badge.img+7
    • rory.smith
    • TimeXtender Xpert
    • 649 replies
    • May 7, 2024

    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
    1 person likes this
    • Christian Hauggaard
      Christian Hauggaard
    Christian Hauggaard
    Community Manager
    Forum|alt.badge.img+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.

    M
    Contributor
    • Marcodenijs
    • Contributor
    • 10 replies
    • July 8, 2024

    @rory.smith Even though really impractical I get it. But the question remains, how am I supposed to know/be warned that something is wrong with my job then? 

    As described Source in ODX Shows no error. | Community (timextender.com) here, I can have a fully functional execution showing me no errors at all while the source is not working/giving me any daya. 

    rory.smith
    TimeXtender Xpert
    Forum|alt.badge.img+7
    • rory.smith
    • TimeXtender Xpert
    • 649 replies
    • July 9, 2024

    Hi @Marcodenijs ,

    I suspect that the Jobs API also does not give you this info - In my opinion an error, but may be good to post an idea just in case.

    Reply


    Most helpful members this week

    Terms and ConditionsCookie settings

    Cookie policy

    We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

     
    Cookie settings