Hello,
I’ve set up a server task based on a “file appears” event. It works fine, but yesterday the server hosting the triggering file shut down and restarted. The task then failed with a “file no longer exists” error message, but it stopped monitoring for the file afterward.
Is there a way to display a warning when the file is not found, while keeping the task running?
Thanks and best regards,
Chris
Hi Chris,
Can you please post a screenshot of the trigger settings?
Hi Dmitry,
I’m afraid it won’t help much, but here it is. When the task doesn’t run (not exactly fails), the cell next to the current state shows something like “folder does not exist or is not accessible,” but it never returns to “The trigger is active” even when the path becomes available again.
This is the correct behavior. Once a trigger fails, it switches into the “error” state (with red bar). It no longer checks the target folder, so it can’t identify if the problem went away or not.
To resume the trigger, fix the cause of the error, and then click the “Retry” button (shown below).
Hi Dmitry,
Maybe this is the expected behaviour, but in my opinion the task should also fail in this situation. When this happened, the server hosting the file was restarted in the afternoon, so the trigger failed, but I didn’t receive any warning and the task didn’t run overnight for several days. A user noticed that the figures were wrong, but we weren’t aware of the issue.
Best regards,
Chris
When a trigger fails and switches to the “error” state, the Server should send an email notification, similar to the notification about a failed task.
Check your Server notification settings to verify if they are configured correctly.
