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"
}
LIfe has been busy lately!
