Files

The Files section is a shared storage area for a project. It holds two kinds of files: uploads added by project members — workflow files, shell scripts, preference files, JDBC drivers, certificates — and artifacts generated by executors as the output of a run. Both types live in the same list and can be referenced by environments and schedules.

Your files

The file list shows all files in the current project. Each file is shown with an icon matching its extension. Use the filter bar at the top to switch between uploaded files and run artifacts, and the search to find files by name. You can also sort by name, size, or last modified date.

Each row has two actions: Download to save a local copy, and Delete — see Deleting a file.

Clicking a file opens its detail view, which shows the name, origin, size, and last modified date. For KNIME workflow files (.knwf), Runner renders a zoomable SVG preview of the workflow so you can identify the file at a glance without opening it in KNIME.

Uploading files

Click Upload Files or drag one or more files anywhere onto the Files page. Multiple files can be uploaded in a single operation. Uploading requires the appropriate project role — the button is disabled if you don't have it. See Members & Roles for details.

There is no restriction on file type. Files are available for selection across environments and schedules as soon as the upload completes. Files can also be uploaded directly from the environment form — preference files and additional files uploaded there appear here in the same list. See Environments for details.

Replacing a file

Open a file and click Replace … to upload a new version. The filename stays the same and all environments and schedules that reference this file automatically use the new content — no need to update them manually. Use this to update a workflow or script without changing any of your schedule configuration. Replacing requires the same project role as uploading — the button is disabled if you don't have it.

Deleting a file

Deleting a file requires the appropriate project role. A file can only be deleted if nothing references it. The Delete button is disabled if the file is currently used by an environment (as a preference file or additional file), a schedule (as the workflow, script, or additional file), or a run (as an artifact). Remove or update those references first.