Debugging a trigger can be useful in the event that the trigger actions for an event are not being executed as expected. The cause for trigger actions not being executed include the following:
1. Trigger not applied - After creating a trigger make sure to click the "Apply" button. Only after clicking the "Apply" button will your trigger be recognized by the server.
2. Action failure - The arguments provided to an action may be invalid or the action may fail for some other reason. For example, an action may be expecting an absolute file path when a relative path has been provided. More information on the cause of action failure can be found in the server log file which can be viewed using the Logging > View log panel found in JSCAPE MFT Server Manager. Many of the network related actions (Ftp File Upload, Send Email etc.) also have a debugging option to capture more information.
You can see a list of action types and their corresponding argument definitions when you add a trigger action to a trigger. Definitions can be seen via a context-sensitive help.
3. Condition failure - The conditions used in a trigger event may be incorrect. To debug this type of situation remove all trigger conditions and add a System Out action to the beginning of your action list that prints the values of the event variables you are using in your conditions to the server log. You can then view the server log using the Logging > View log panel found in JSCAPE MFT Server Manager to compare against your conditions.
4. Event failure - The event type you are listening for may be incorrect.
You can see a list of event types and their corresponding definitions in the first step of the trigger creation process. Definitions can be seen via context-sensitive help.