If the scheduler does not work probably, you usually get an e-mail with an included link that starts with
The link contains further information about the scheduler entity that has been harmed. In order to find out what is wrong, please click on ‘Details’ and look at the ‘Debug message’-field and the ‘Message’-field at the bottom of the scheduler. If the left one is empty, it is OK. The right one is filled anyway. If an error message is displayed in both fields, your fetch or workflow is incorrect. In that case, please copy the information from both fields and send an e-Mail to firstname.lastname@example.org.
Figure 1: MSCRM-ADDONS.com scheduler with error message
Please note: If you do not get an e-Mail with the error-message, you must open the scheduler manually. To do so, please follow this blog article (but do not activate the scheduler) and please proceed as above shown.
Furthermore, you have the possibility to check the background processes. To do so, please open the drop-down menu and click on Background Processes in the Process Sessions-section.
Figure 2: Open the Background Processes
Next, open the MSCRM-ADDONS.com scheduler process from the list you are provided with.
Figure 3: Open the MSCRM-ADDONS.com scheduler
In the so opened window, you get some further information about the scheduler error.
Please note: If the window is empty, the scheduler will not work anymore, no matter what you do.
In that case, the only possible way to solve the problem, is to create a new scheduler with the same values and to check if the background processes are available in the newly created scheduler. Also, please delete the old scheduler.
If the window looks similar to figure 4, please follow the below steps:
Figure 4: Further information about the scheduler
If you get an error message again, please restart the process.
If the problem continues, please click on Details to show the specific error message.
Copy all information from the details field and send an e-Mail to email@example.com.
That’s it! We appreciate your feedback! Please share your thoughts by sending an e-Mail to firstname.lastname@example.org.