Skip to main content



Here you can configure the Internal Processing Node of FileFlows. A Processing Node is what executes a Flow and processes Files.

  • Enabled
    • When disabled no files will be processed by the Internal Processing Node. You can disable this if you wish to pause the system.
  • Flow Runners
    • The number of flow runner instances available to execute a flow.
  • Temp Directory
    • This directory will be used by flows to create temporary files as the flow is processed, this directory will be regularly cleaned up so keep nothing important here.
  • Schedule
    • This allows you to configure when files can begin processing. No files will begin processing outside of this schedule.


  • Log Queue Messages
    • This will cause excessive logging of all files being queued/dequeued in the library watcher.
    • Turn this if you are having issues with files not appearing, turn off again afterwards to avoid filling your log files with excessive logging.
  • Log Every Request
    • If every request to the server should be logged.
  • Log File Retention
    • How many log files to keep before deleting older log files.
    • Each log file is up to 10MB in size.
  • Log Database Retention
    • The maximum number of records to keep when the database log pruner executes.
    • Note the table is not limited to this number, as it can grow after the pruner runs, but when the pruner runs only this amount will be kept.
  • File Added Notifications
    • If a toast notification should be shown in the web console when a file has been found and added to the queue.
  • Processing Started Notifications
    • If a toast notification should be shown in the web console when a file begins processing
  • Processing Finished Notifications
    • If a toast notification should be shown in the web console when a file finishes processing


  • Checks for Update
    • Checks for an update now and if found will download the update and install it when no Flows are executing.
  • Auto Update
    • When enabled FileFlows will routinely be checked for updates, and if an update is found, will automatically be downloaded and installed.
  • Auto Update Plugins
    • When enabled plugins will routinely be checked for updates, and if any updates are found will automatically be downloaded.
  • Auto Update Nodes
    • When enabled external nodes will automatically update when FileFlows server updates. Meaning you will only have to update the FileFlows server instance in a distributed environment.


  • Type
    • The type of database to use, the default type is SQLite which requires not additional setup or configuration
  • Server
    • The address of the Database server and the port or named instance if required
  • Name
    • The name of the database to created, if left blank 'FileFlows' will be used
  • Port
    • The default port for MySQL is 3306
  • User
    • The user used to connect to the database
  • Password
    • The password of the user to connect to the database


Tests the database connection

Restart FileFlows

This will save the database connection are restart the FileFlows server.


  • Telemetry
    • Telemetry is useful to help know what devices we need to support, what Flow parts are the most used and where we should focus on the development. All data is anonymous and no information about what files were processed will be sent.
    • If telemetry is disabled all auto updates will also be disabled as they do contact which is a form of telemetry.
  • Keep Failed Temp Files
    • Enabling this option will retain the temporary files used by a flow in case of failure, preventing them from being automatically deleted.
    • Use with caution.