Recently active topics

A question that comes up often: is there a log that shows who last modified a job or schedule? The answer is yes, but it is not in the system log files. OpCon maintains a comprehensive audit trail of all object changes in the database, and you access it through the Reporting section in Solution Manager.Where to Find ItThe Audit History report is located in the Reporting section of Solution Manager, not under Logs. To get there:In Solution Manager, go to Library and navigate to Reporting Select Audit History from the reports listThe report opens with columns for Date & Time, Username, Machine, Data Changed, Original Value, Final Value, Category, and Name.Filtering the ResultsEvery change made to an OpCon object is automatically recorded in the database. This happens continuously in the background without any configuration required. To narrow it down to what you are looking for, use the filter icon on any column header to add filter criteria. All columns can be used as filters: Date

When OpCon has trouble communicating with an agent, the SAM log can give you a general indication that something is wrong. But if you need the specifics, the NetCom log is where you go.What the NetCom Log ContainsNetCom (Network Communications Module) is responsible for all TCP/IP communication between the SAM process and the agents (LSAMs) running on your machines. The SMANetCom.log records:Agent configuration parameters as they are loaded (changed parameters are shown alongside their default values in parentheses) Basic communication information for each agent machine Connection events: when communication is enabled or disabled for an agent Machine status changes Errors when a connection cannot be established, such as DNS name resolution failuresReading the NetCom Log Alongside SAMA common troubleshooting pattern is to start in the SAM log to get the high-level picture, then move to the NetCom log for detail. For example, if SAM shows a machine status change, the SAM log tells you wh

OpCon gives you three primary tools for controlling when and in what order jobs run: job dependencies, resources, and thresholds. All three are valid, and experienced OpCon administrators often use all three in the same environment. Understanding the strengths, and the right use case, for each will help you design cleaner, more resilient automations.Job Dependencies: Best for Sequential, Linear ProcessesJob dependencies are the right choice when Job B genuinely cannot start until Job A has finished, and when the order matters. If you're building a workflow where data flows from one process to the next, job dependencies create that hard link. They're explicit, easy to read in the workflow view, and appropriate for processes with a defined sequence.Limitation: Job dependencies wait for a job's final completion state. If a job is configured to restart and repeat throughout the day, a downstream job dependency won't trigger until all restarts are complete, which may be far later than you n