---
title: "Submission results request based on Verdict and Status"
slug: "submission-results-request-based-on-verdict-and-status"
tags: ["Reference"]
updated: 2026-10-13T05:16:48Z
published: 2026-10-13T05:16:48Z
canonical: "docs.trellix.com/submission-results-request-based-on-verdict-and-status"
stale: true
---
> ## Documentation Index
> Fetch the complete documentation index at: https://docs.trellix.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Submission results request based on Verdict and Status
Describes all possible combinations of verdict and status returned by the `/result` endpoint following a file or URL analysis.
```plaintext
GET https://
/wsapis/mvx/v2.0.0/submissions/result/
```
### Parameters:
- **address**: IP address of the IVX appliance.
- **uuid**: The unique submission identifier returned during the submission process.
- **API-Token**: Session token obtained from the authentication request.
### Response
- **status**: Indicates the current state of the submission analysis.
- queued: Analysis is waiting for available resources.
- success: Analysis completed successfully.
- failed: An error occurred during analysis.
- **verdict**: The security assessment of the analyzed object.
- malicious: The object contains known or behavioral malware.
- riskware: The object is potentially unwanted or contains security risks.
- non-malicious: No malicious behavior or signatures were detected.
### Submission analysis status
The following table provides detailed descriptions for the generic statuses returned by the IVX engine during the submission.
| Generic Status | Description |
| --- | --- |
| Success | Indicates successful execution of the file. A verdict of Malicious, Riskware, or Clean/Non-malicious is expected. |
| File Empty | The submitted file, the object pointed to by a URL, or the contents extracted from an archive are empty. |
| Download Empty | Indicates a download failure, such as an embedded object failing to download or a URL target being unreachable. |
| Submit Error | Submission failure caused by stopped services, malformed requests, or improper parameters. Primarily applicable to sensor-based submissions. |
| Overlimit Error | The submitted archive exceeds configured limits, such as maximum file count or recursive archive levels. |
| ISO Create Error | Failure occurred during the creation of the analysis image. |
| Duplicate | A previous analysis result for this object is already available. |
| Submit Whitelist | The file, user, or URL is whitelisted or explicitly allowed by existing policy. |
| Submit Disabled | The file type is unsupported, no matching analysis profile was found, or the file is too large for the current configuration. |
| Invalid | Indicates an invalid file or a bad request/response from FENET. |
| Submit Timeout | The file was not picked up for analysis within 24 hours or a component failed to respond in time. |
| File Unknown | The submitted file type is unknown to the system. |
| Force Terminate | The file analysis was forcefully terminated during execution. |
| File Limit | The submitted file exceeds the maximum size allowed for analysis. |
| Download Limit | The size of the file being downloaded via URL exceeds the allowed limit. |
| Static Analysis Only | The file was identified as clean by the pre-filter. (Applicable only to PDF, HTM, and XLS files) . |
| Aborted | The submission was manually or systematically aborted. |
| VM Failed | An error occurred during analysis where the Virtual Machine failed to initialize, crashed, or the analysis engine died. |
| Download Failed | Failure during the prefetch stage due to malformed URLs, too many redirects, or unsupported protocols. |
| Download Could Not Resolve Proxy | Failure to resolve the proxy for download. |
| Download Could Not Resolve Host | Failure to resolve the host for download. |
| Download Could Not Connect | Unable to connect to the URL for download. |
| Download Access Denied | Client configured access policy to deny download requests. |
| Download Timeout | The download operation timed out. |
| Download 404 Not Found | Download failure due to a "File Not Found" (404) error. |
| Bypass | Specific to EX appliances when an email is bypassed for any reason (not applicable for VX). |
| Password Protected(failed) | Archive extraction failed because the password was incorrect. |
| Extraction Failed | The system failed to extract the archive or the provided password was incorrect. |
| Failed | Internal system component failure (e.g., Database error, File Access error) resulting in an inconclusive analysis. |
| Unknown | Analysis behavior is uncertain or non-deterministic. |
### Example request
```plaintext
GET https://10.128.32.232/wsapis/mvx/v2.0.0/submissions/result/5e9e81e4-c48a-481e-b4ec-02c3f917f9a5
```
### Example response
JSON:
```plaintext
[Result Data]
{
"uuid": "5e9e81e4-c48a-481e-b4ec-02c3f917f9a5",
"status": "success", "verdict": "malicious",
"complete_time": "2026-02-05T05:50:32.835Z",
"sha256": "140417ba2238dde6de6b541ad75dae6a96fec5d7482054dc154242a1992c9b2f"
}
```
: