FileZilla Queue Completion Alerts – Missing Per‑Site Override

The Short Answer

FileZilla does not provide a native per-site override for queue-completion notifications. The settings in the Notifications panel are global. However, you can achieve a per-site exception by disabling the built-in sound alert and using the "Run program" action to trigger a custom script that filters alerts based on the connection host.

How the Workaround Works

While the notification trigger is global, FileZilla passes specific metadata to any external program it executes. By routing the alert through a script, you can inspect the host variable and decide whether to play a sound or exit silently.

Implementation Steps

1. Disable Global Sound: Go to Edit → Settings → Notifications. Uncheck the box for the "Queue completed" sound alert to prevent the global notification from firing.
2. Configure the External Script: In the same Notifications panel, check the "Run program" box for the "Queue completed" event. Point this to a script (e.g., .bat, .ps1, or .sh) designed to handle the logic.
3. Use Placeholders: Use the %h placeholder (which represents the host) to pass the site identity to your script.

Example Logic (Windows PowerShell)

You can use a simple PowerShell command to filter out specific hosts. Replace silent-site.com with the host you wish to mute:

powershell -Command "if ('%h' -ne 'silent-site.com') { [System.Media.SystemSounds]::Asterisk.Play() }"

Assumptions and Technical Constraints

• Version Dependency: This solution assumes your version of FileZilla supports the %h (host) placeholder for the "Queue completed" event.
• Execution Overhead: Because an external process is spawned, ensure the script is lightweight. A hanging script may delay the finalization of the FileZilla UI state.
• Security: Avoid using placeholders like %u (username) or %p (password) in scripts, as these may be logged in plain text by the OS process manager.

Verification Method

To verify that the correct host data is being passed, point the "Run program" field to a simple logging command first:

cmd /c echo %h >> C:\temp\fz_test.txt

Complete a transfer to your target site and check the text file. If the hostname appears correctly, the conditional logic in the PowerShell example will function as intended.