Download pipelines
Some forums run automated checks on downloadable files. These checks can scan for malware, validate an archive, or perform other tasks configured by the forum. Multiforum calls the sequence of checks a pipeline.
Viewing checks
When a download has configured checks or previous check history, its detail page includes a Pipelines tab. Anyone who can view the download can see:
- which checks apply;
- whether each check has run;
- current and previous attempts;
- when each attempt started and finished;
- public results and remediation guidance;
- who started or approved an attempt.
Pipeline history follows the visibility of the download. It is public for a public download, but it does not make private, unpublished, or removed content visible.
Understanding statuses
| Status | Meaning |
|---|---|
| Not required | The forum's rollout policy excludes this file. |
| Not executed | The check is required, but no attempt has run yet. |
| Queued | The attempt is waiting for a worker. |
| Running | At least one check is in progress. |
| Passed | All required checks completed successfully. |
| Failed | A check reported a failure. |
| Timed out | The attempt stopped making progress and expired. |
| Cancelled | The attempt was cancelled before completion. |
| Manually approved | An authorized moderator approved the result. |
Not executed is different from a check that is currently pending. It often appears when a forum adds a check after a file was uploaded but chooses to require that older file to be checked.
Starting and retrying checks
The original uploader can select Run checks for a required check that has not run. Uploaders and authorized moderators can select Run checks again after an eligible failed, timed-out, or cancelled attempt.
Retries:
- use the forum's current enabled pipeline configuration;
- create a new attempt without changing the previous history;
- apply to the same uploaded file version;
- may be subject to a cooldown and retry limit;
- cannot start while another attempt for that file and pipeline is active.
Replacing the file creates a new file version, which is evaluated separately.
Sharing results and getting help
Each attempt has a stable URL. Use Share this attempt to send someone directly to it, or Copy diagnostics to copy the intentionally public result. Ask the community starts a support discussion containing the attempt ID and diagnostic code.
Public diagnostics are designed to be safe to share. Private plugin logs, credentials, storage locations, and provider internals are not included.
Pipeline completions and timeouts may also appear in uploader notifications and in the download's Activity tab.
Quarantined downloads
When a required security check has not produced a clean result, Multiforum places the file on a logical hold. The file remains attached to its discussion, but direct download is disabled.
| File state | What it means | Uploader action |
|---|---|---|
| Security check pending | The file is waiting for or running a scan. | Open Pipelines to check progress. |
| Suspicious content | The scanner found something needing human review. | Review the finding, replace the file, retry, or request human review. |
| Threat detected | The scanner reported malware. | Remove or replace the affected content before retrying. |
| Security check incomplete | The provider or plugin could not finish. | Retry later; open an issue if it repeats. |
| Available to download | The current file version is clean or was released after review. | No action is needed. |
Other visitors can see that a file is quarantined and its public diagnostics, but they cannot download it. Scanner credentials, provider responses, private storage URLs, and internal logs are never part of the public result.
If you request human review, explain why you believe the file is safe. A reviewer can release quarantine only with a recorded reason. The pipeline history remains visible so the community can understand what happened.
If a check appears stuck
Refreshes and open browser tabs do not control pipeline execution. A background watchdog detects abandoned jobs and changes them to Timed out, after which an eligible uploader or moderator can retry.
If an attempt remains queued or running beyond the time shown by the forum, share its stable URL with a forum administrator.