The Loupe Agent supports two methods of automatically sending session data.  These methods can work together, but are designed for different situations.  You may want to use either or both of them in your application.

1. Auto Send Sessions:  This is an option of the Server configuration that when enabled will have the agent periodically check for new sessions to send as well as automatically send the current process information when there is an error.  It supports the Loupe Server only, and can optionally remove information from the local computer when complete.
2. Send Sessions On Exit:  This is an option that can be set on the Log object indicating that once the current process exists the Loupe Packager should send all new sessions.  It supports sending to Email and the Loupe Server, picking the Server in preference if it is configured and accessible. 

Comparing Options

Auto Send Sessions

• Sends partial session information automatically whenever fragment files are closed.
• Can send the current session immediately after the session is closed (when the process/application domain exits) if the Packager Utility is shipped along with the Agent, or the next time the application is run if the Packager is not available.
• Only supports sending sessions to a Server.
• Does not require any files beyond the Agent. 
• Automatically resumes transfer whenever your application is running after an OS shutdown or user logout.  As long as any user on the computer is running one of your applications the session data will transfer.
• Does not require permission to start a process, only the ability to open an HTTP(s) connection.

Send Sessions On Exit

• Can send the current session immediately after the session is closed (when the process/application domain exits).
• Will only send sessions when you request.
• Supports both Email and Server.
• Requires the Packager Utility be shipped along with the Agent. 
• Sends full session information for all new (unsent) sessions even if the Server would not request the detail under the current configuration.
• Can't resume if stopped by OS shutdown or user log out (for applications running as a specific user)
• Requires the permission to start a process to work.

Working Together

These methods are designed to work together to cover the broadest range of user scenarios.

• Safe Together:  The Packager can be run independently or as part of sending sessions on exit without interfering with other instances of your application that are currently automatically sending sessions. 
• Avoids Duplicate Work:  If the session is sent during the Send Sessions On Exit process to the Server it will not be subsequently sent during the Auto Send process.  If it is currently being sent by the Auto Send process it will be skipped by the Packager.

Scenario One:  Immediately send sessions as soon as applications exit

If you have configured Server integration this will be done automatically just by setting the AutoSendSessions option.  Otherwise, you can do this over email by setting the SendSessionsOnExit property each time the application starts.

Scenario Two:  Sending error sessions

If you have configured Server integration this will be done automatically just by setting the AutoSendSessions option.  Otherwise you can take advantage of the Log.MessageAlert event to both set the SendSessionsOnExit property and immediately send the partial (active) session in the event of an error.

Scenario Two:  Sending error sessions when a user has declined to participate in your CEIP

If you are providing an opt-out capability for your Customer Experience Improvement Program then some users will elect to not automatically send their data.   In the event of a problem they may change their minds and be willing to submit data.  If you are using the Loupe Error Manager the user will be able to simply check a box when faced with an error and enable SendSessionsOnExit.  This will then send their information this one time, enabling you to see both the immediate session that they were concerned about in full and the other sessions for your application that were still in the local repository (subject to your pruning limits).