Senergy's event processing model is designed to require a minimum of administrator oversight once policies are created. However, there are circumstances that require an administrator to examine and analyze events on the pending events queue. If an event did not fail with an error that prevented the event from completing, it might instead go into a "bypassable" state.
Senergy is designed to be deterministic. When policy calculation is complete, the Senergy Engine has determined exactly what actions should be taken to process an event. Occasionally, though, the Senergy Engine needs information that can't be determined programatically, and must come from an administrator.
In these cases, the event in question goes into a "bypassable" state. This means that the event will not proceed further until a Senergy administrator examines the event and makes a decision on whether or not it should complete.
If the event should not complete, administrators need to decide how to deal with the situation. If the event is simply erroneous, it should be aborted. If it would normally be correct, but letting it proceed immediately would be problematic, the event can be left on the queue until whatever issue in the environment requires resolution, is resolved.
If the event should complete, administrators can use the "Bypass" option in the Events queue to permit the event to continue. This can be done using the "Bypass" button, or by right-clicking on the event and choosing the "Bypass" option. (Note that if multiple bypassable events are selected, the "Bypass" option will work on all of them with one click; but if a mix of bypassable and non-bypassable events are selected, the "Bypass" option will be unavailable.)
Pre-existing managed paths
The most common use case for the "Bypass" option is a simple one: The Senergy Engine determines that a particular managed path should be created, but a folder with that name already exists in the target path location.
For example, John Smith is a new user in an organization. According to the organization's Senergy policies, this user's home folder (based on their SAMAccount name) will be \\server\share\homes\jsmith. Their Active Directory account is created, ultimately generating a Set Policy event in Senergy.
However, someone else has already manually created this \\server\share\homes\jsmith folder, before Senergy detected the event which triggered the Set Policy event. In this case, Senergy will put the event into a "Bypassable" state (and will return a last error condition of "28: File system path already exists", visible in the event's details.) It is of course likely that this is indeed the path Senergy should assign as this user's managed path; but since the Senergy Engine did not create the path itself, an administrator has to verify that the Engine should proceed using that path. The administrator can use the "Bypass" option described above to permit it to continue.
What if, though, this \\server\share\homes\jsmith path was not manually created by another user for John Smith? Perhaps there's a different user already using this path for their home folder. In that case, if the event were to proceed, that user would lose access to their home folder and John Smith's home folder would contain all of that user's files. Or perhaps this path is a home folder belonging to a user no longer in the organization. In either case, the administrator would not want this event to proceed. They might abort this event; or they might move or rename the extant \\server\share\homes\jsmith path in order to preserve this data and permit the event to proceed on the next attempt.