These are the general rules that apply for persisting a temporary file

Connection type	Persistence	Clustered	Notes
Memory	Temporary	No	The file is stored temporarily for the duration of the current request. At the end of the request the file is deleted. Memory connections and temporary persistence should be used when an uploaded/received file is immediately sent to a 3rd party system during the same request.
Memory	Temporary	Yes
Other / FileSystem	Temporary	No	The file is stored temporarily for the duration of the current session. At the end of the session the file is deleted.
Other / FileSystem	Temporary	Yes	The file is stored temporarily for the duration of the current session and a Quartz job is scheduled to delete the file after the session has expired.

Note: It is possible to enter a file size in the file upload container that is larger than accepted by the system (network or server settings for example). In that case the network/server setting will overrule this size.

Temporary memory

The Blueriq Runtime stores the file inside the Runtime's memory, no matter if it is running as a single environment or in a clustered environment.

If the file is larger than the heap size on the system, the user will receive an error.

Temporary file store

Running the environment in a clustered or unclustered environment will store the file temporarily for the duration of the current session. At the end of the session the file is deleted.

For the normal single Runtime configuration, the file is deleted automatically when the session expires.

Cluster environment

For running Blueriq in a cluster configuration, and to control on what node will execute the deletion of the file, the Blueriq Scheduler Component is used, thus, it must be enabled and configured accordingly.

Some notes to take in consideration when running the Blueriq Scheduler and a cluster configuration:

If the Blueriq Scheduler is not configured when running in a cluster, the upload of the files will work but never be removed from the file system. A warning log will appear in runtime, but a manual deletion of the file is required
If the Blueriq scheduler is configured to use in memory database, restarting the runtime will not triger again the deletion of the file and can result in files remaining undeleted
Make sure the (shared) file system can be accessed by all the runtimes in the clustere