File watcher event no longer starts as expected via jsch.
Release : 12.3.8
Component : AUTOMATION ENGINE
Issue did not reoccur after a restart of the agent.
Usually there's more to the message than reason being blank (''). If this issue is observed, it's best to set a tcp/ip=9 trace on the agent where the event is running (this can be done by going to the Administration perspective, Agents, right-click the agent, choose Advanced Options, set tcp/ip to 9, be sure that "Memory trace" is unchecked, hit Apply) and reproduce the issue with the tracing turned on. Then send the agent log and trace as well as the details of the object that fails - In Process monitoring, find the run that fails, click on the "Details" button in the upper right, Copy the full text or send screenshots of the Details that show up there.