Not sure if this was upgrade related or what, but just noticed that the scheduled jobs do not seem to be running. So things like getting the latest version of an existing app from Apple or devices being queried from time to time are not happening. All the jobs show last successful completion as blank and as an example this is the details:
Name MDM Application List Sample
Frequency Every 2 Minutes
Last Start Time 1/1/0001 12:00 AM
Last Successful Completion 1/1/0001 12:00 AM
Number Of Times Run 0 time(s)
Status Waiting
Funny enough in this job it says the minimum frequency should be 10 minutes so not sure if they changed that and left the defaults and if it's then still working or not. All services show running on all the servers. Any thoughts? This is 1902 Thanks. Steve
Restarting the Device Scheduler service has temporarily resolved the issue for me in 2005 on-premise. It was also working every time the server rebooted but that was overkill. Glad to hear support has some ideas. I will be putting in a ticket the next time I see scheduler has stopped working and will reference this forum thread. Glad to hear you're still solving issue Luke!
I put in a ticket to see what ideas they have: Your support request number is 20150684408.
I do what I can LIfe has been busy lately!
So here is what support had me do a while back:
After doing some digging, I found there have been some Scheduler improvements with In-memory scheduling. In console 1904, we automatically set the 'InMemoryScheduleryFeature' flag set to true. This allows the service to continue running even during a DB outage. Starting in console 1811, this option is available, but we must turn it on manually.
Here are the steps you will need to take to enable this:
1. Get the Global OG UUID from the following db query:
select LocationGroupUUID from LocationGroup (nolock) where locationgroupid = 7
2. Call the following API
https://<host>/api/system/featureflag/InMemorySchedulerFeatureFlag/<GlobalOGUUID>/true
where GlobalOGUUID is your UUID. retrieved from the step above.
Method: POST
Here are headers that are required:
Headers:
authorization: Basic [Base64 Encoded Credentials]
content-type: application/json
aw-tenant-code: [API Key]
accept: application/json
Expected response should be 204 No Content
3. Validate if Feature Flag is enabled by calling the following api. Expected response is 200.
https://{host}/api/system/featureflag/InMemorySchedulerFeatureFlag/{GlobalOGUUID}
Method: GET
with the following response:
{
"name": "InMemorySchedulerFeatureFlag",
"isEnabled": true,
"state": "Production"
}
While I no longer worry about the job scheduler not running as a Saas customer, we did run into an issue a couple of times where one of the jobs for device compliance wasn't running and no one knew about it since the job scheduler was running fine.
I have fixed my problem by making changes in task conditions.