sql server agent says that a job is running but the step says it has finished

Igor Gelin 21 Reputation points


We have a subscription for a SSRS report. The job in the agent says it is running.

Date 3/24/2022 5:30:00 PM
Log Job History (2669F99D-D502-40EC-8AF0-716394C50CBD)
Job Name 2669F99D-D502-40EC-8AF0-716394C50CBD
Duration 16:11:37.4270000
In progress

But the step finished.

Date 3/24/2022 5:30:00 PM
Log Job History (2669F99D-D502-40EC-8AF0-716394C50CBD)
Step ID 1
Server MyCoolServer
Job Name 2669F99D-D502-40EC-8AF0-716394C50CBD
Step Name 2669F99D-D502-40EC-8AF0-716394C50CBD_step_1
Duration 00:00:01
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0
Executed as user: NT AUTHORITY\SYSTEM. The step succeeded.

Why would the agent report the job as still running (for 16 hours) while the only step in the job finished in 1 second?


SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
13,105 questions
SQL Server Reporting Services
SQL Server Reporting Services
A SQL Server technology that supports the creation, management, and delivery of both traditional, paper-oriented reports and interactive, web-based reports.
2,850 questions
0 comments No comments
{count} votes

4 answers

Sort by: Most helpful
  1. Naomi 7,366 Reputation points

    Hi Igor,

    Did you find an answer to your question? I have a similar problem recently which I'm not sure how to figure out. I receive alerts that the job failed, however I see nothing exactly that indicates any failure and when I view the failed job history report we have on the production server I see: "The step did not generate any output. Process Exit Code 0. The step succeeded." The only explanation I may have that the custom report is somehow wrong or gather information wrongly?

  2. Isabellaz-1451 3,616 Reputation points

    Hi anonymous userGelin-0063
    SSRS doesn’t have its own built-in scheduling engine and instead uses SQL Agent. Whenever a subscription is created, a corresponding SQL Agent job is created that is scheduled to run according to the scheduling parameters for that subscription.

    I think it make sense that the job duration is longer than the step duration,cause job is consist of many steps,and this step finished,maybe there are many other steps that you don't know. Or this is a long run job not once.

    Best Regards,

    If the answer is the right solution, please click "Accept Answer" and upvote it. If you have extra questions about this answer, please click "Comment".
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

  3. Igor Gelin 21 Reputation points

    It is "One Time".

    0 comments No comments

  4. Igor Gelin 21 Reputation points

    Any help on this?

    0 comments No comments