08-13-2024 07:42 AM
Good morning,
In our activity log, where our instances are monitored, is there a way to detect if an instance stops processing? We have had some cases where our end users noticed their documents were not importing. I aim to be proactive and let our end users know we are working on it before they know there is an issue.
Thank you!
08-13-2024 08:25 AM
Hi
That depends on what causes the process to stop. If the Unity Scheduler instance's Windows Service is in Stopped state, when you know that the process is not running because the Windows Service is not running. Starting the Windows Service would start the processes again. Reviewing the Windows Event Viewer logs would likely provide more information as to why the Windows Service stopped.
Here are some links which can help you build a script to query the statuses of the process ...
The other scenario is where the Unity Scheduler instance's Windows Service is in a Running status, but the underlying process is not doing any work (e.g. the Unity Scheduler process may have encountered an error message). For this scenario you would have to review the Hyland Diagnostics logs from the Unity Scheduler instance to determine if there is a problem preventing the Unity Scheduler instance from executing a particular Task.
You can configure the Unity Scheduler instance to log to the Hyland Diagnostics Service by updating the .config file according to the Hyland.Logging settings ...
Alternatively, you could build a Reporting Dashboards Report to track processing over time so you know when the processes is not working as expected.
Best wishes.
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.