OS4X fetch queue
With OS4X fetch queue, you are able to automatically collect files from remote servers via various protocols. Feel free to ask for extended protocol support by submitting your request to support@os4x.com.
Required license
OS4X fetch queue comes in different license models:
- Stand-alone license (only OS4X fetch queue is licensed)
- Add-on license for OS4X Core
- Included in OS4X Enterprise
The OS4X fetch queue is visible in:
- Queues -> Fetch queue
The logs are visible via:
- Logs -> Fetch queue log
Configuration
Dry-run
When starting a dry-run of an OS4X fetch queue entry, the server is being connected to and the directory is listed for potential files which may be fetched. The files are being examined for regular expression and age information. If these tests succeed, an output will be printed out which displays what will be done afterwards. No file will be transferred during this process, also not deleted. If verbose output is enabled, all protocol information are being contained in the output window.
Logging
The logs in "Logs" -> "Fetch queue log" contain all information about fetching processes. If an OS4X Enterprise job is being created, it is directly viewable via the "info" icon on the left.
Daemon
The background daemon running OS4X fetch queue is "os4xfqd", which is installed in OS4X's binary directory.. The daemon can be started and stopped from the top-left icon list:
Alternatively, you can manage the process at the panel "Programs" -> "Daemons":
Supported protocols
Starting at 2025-08-20, OS4X fetch queue supports the following protocols:
- FTP
- Implicit FTPS
- Explicit FTPS (via STARTTLS)
- SFTP
- WebDAV (via http)
- WebDAV (via https)
Why no SCP? - Well, the SCP protocol doesn't support a "delete" operation, so fetched files cannot be deleted from the source server, making it impossible to distinguish between already fetched files and new ones.