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

Improved: use scheduleService action instead of runServiceNow for Initial load job (#423) #437

Merged
merged 1 commit into from
Apr 11, 2023

Conversation

adityasharma7
Copy link
Contributor

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

Additional change:
Removed fetch jobs action cal for runServiceNow as the jobs which reflects through this action must have temp expression. Thus run now has no effect on current jobs.

Related Issues

Closes #423

Short Description and Why It's Useful

Screenshots of Visual Changes before/after (If There Are Any)

IMPORTANT NOTICE - Remember to add changelog entry

Contribution and Currently Important Rules Acceptance

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 adityasharma7 merged commit f6c8f02 into main Apr 11, 2023
@adityasharma7 adityasharma7 changed the title Improved: user scheduleService action instead of runServiceNow (#423) Improved: use scheduleService action instead of runServiceNow for Initial load job (#423) Apr 11, 2023
@adityasharma7 adityasharma7 deleted the #423 branch July 19, 2023 13:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Run now functionality not working for already runnning job
1 participant