Yamen Alghrer

That seemed to do it, you're a lifesaver Andreas!! The odd thing is that I have no clue where this eMailDefault job resource even came from. I never created it or even included it in my notifications.xml. Attached is what the gui for my JOC notifications looked like when I sent the file over to you. The eMailDefault job resource wouldn't go away even when I tried re-deploying the notifications configuration page. I had to go into the XML and edit it out manually, which finally did the trick. I really...

Hey Andreas, Thank you so much for the quick and thorough response! Regarding your two observations: 1) I went ahead and took your advice to remove the job specific notifications from the test job and keep it all in the Notifications configurations. 2) I tried removing the "To" and "From" from the notification settings in my notification.xml and kept it all in the EmailJobConfigurationOps resource, but I'm still receiving this NullPointer Exception. I tested to make sure that my EmailJobConfigurationOps...

Hello, I too am having a really hard time setting notifications up in order to send emails on either success or error. @sosap I followed the article you linked above which was super clear. It looks like everything is set up on my end, but every time I try and run a test job to see if the feature is working, no email gets sent out and all the logs tell me is that there a NULL pointer Exception error occurred which doesn't really tell me much. Attached is my service-monitor.log, my configuration setup...

Hello, I have this job order with the following configuration: job: /MDG/CoreRebase File timestamp: 24.02.2020 18:28:31 <job order="yes" stop_on_error="false" title="Rebase Core Table Views"> <settings> <log_level><![CDATA[debug9]]></log_level> <history><![CDATA[yes]]></history> <history_with_log><![CDATA[yes]]></history_with_log> </settings> <script language="shell">&lt;![CDATA[<br> cd "C:\Program Files\ETLApp\ETLAppEnv_3_7\Scripts\"</p> <p>.\python.exe -m MDGJobs.LoadCoreData --rebase<br> ]]&gt;</script>...

Hey Anuj, That was exactly it. I had the order job executing as part of a job chain that runs two order jobs consecutively on a weekly basis, while I needed that order job to also run alone on a daily basis...I didn't realize that that would cause an issue for the Job Scheduler. I took your advice by creating a standalone job for the daily run of the job. I'm no longer seeing the "not_in_period" status. Thank you so much for such a quick and helpful response! Thank you, Yamen Alghrer

Hello, I have this job order with the following configuration: job: /MDG/CoreRebase File timestamp: 24.02.2020 18:28:31 <job order="yes" stop_on_error="false" title="Rebase Core Table Views"> <settings> <log_level><![CDATA[debug9]]></log_level> <history><![CDATA[yes]]></history> <history_with_log><![CDATA[yes]]></history_with_log> </settings> <script language="shell">&lt;![CDATA[<br> cd "C:\Program Files\ETLApp\ETLAppEnv_3_7\Scripts\"</p> <p>.\python.exe -m MDGJobs.LoadCoreData --rebase<br> ]]&gt;</script>...