You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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?
Environment details
Additional information
The text was updated successfully, but these errors were encountered: