Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Run now functionality not working for already runnning job #423

Closed
2 tasks
appurvajain opened this issue Apr 7, 2023 · 0 comments · Fixed by #425 or #437
Closed
2 tasks

Run now functionality not working for already runnning job #423

appurvajain opened this issue Apr 7, 2023 · 0 comments · Fixed by #425 or #437
Assignees
Labels
bug Something isn't working

Comments

@appurvajain
Copy link

Current behavior

When we schedule a job and then run the job using the run now function, it picks up the runtime of the scheduled job and does not run instantly.

Expected behavior

When 'run now' function is uses, the jobs should run instantly.

Steps to reproduce the issue

Can you handle fixing this bug by yourself?

  • YES
  • NO

Environment details

  • Browser:
  • OS:
  • Code Version:

Additional information

@appurvajain appurvajain added the bug Something isn't working label Apr 7, 2023
@adityasharma7 adityasharma7 changed the title Run now functionality not working Run now functionality not working for already runnning job Apr 7, 2023
adityasharma7 added a commit that referenced this issue Apr 7, 2023
Fixed: Run now functionality not working for already runnning job (#423)
adityasharma7 added a commit that referenced this issue Apr 11, 2023
Initial load job performs bulk operation and preferred to be run as system user. If the user associated with job is disabled, or password changes, the job may not run
adityasharma7 added a commit that referenced this issue Apr 11, 2023
Improved: user scheduleService action instead of runServiceNow (#423)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment