# disappearedIssuesInput
Input parameters for retrieving disappeared issues with filtering and pagination.
### Examples
```graphql
input DisappearedIssuesInput {
scanID: String
limit: Int!
offset: Int!
sort: DIssuesSort
owners: [String]
tagIds: [String]
inventoryFilters: [InventoryTypes]
dateRange: DateRange
search: [AutoCompleteSearch]
openItems: [FilterTypes]
conditionalFilters: [ConditionalFilters]
exportsOptions: IssuesExportOptions
restrictToCategories: [Int]
topLevelSearch: String
topOffset: Int
issueId: String
scrollDirection: String
cursorValue: String
}
```
### Fields
| Field | Description | Supported fields |
| ---------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| scanID `String` | Specific scan identifier to retrieve disappeared issues from | |
| limit `Int!` | Maximum number of results to return (default: 10) | |
| offset `Int!` | Number of records to skip for pagination | |
| sort [`DIssuesSort`](/api-documentation/api-reference/api--issue/types/inputs/d-issues-sort.md) | Sorting configuration for the disappeared issues | fields \[IssueSortByFields]
order \[Direction]
|
| owners `[String]` | Filter by application owners | |
| tagIds `[String]` | Filter by tag identifiers for role-based access control | |
| inventoryFilters [`[InventoryTypes]`](/api-documentation/api-reference/api--issue/types/enums/inventory-types.md) | Inventory type filters for the issues | |
| dateRange [`DateRange`](/api-documentation/api-reference/api--application/types/inputs/date-range.md) | Date range filter for when issues disappeared | from Float
to Float
|
| search [`[AutoCompleteSearch]`](/api-documentation/api-reference/api--application/types/inputs/auto-complete-search.md) | Advanced search filters with autocomplete support | fieldName String
value \[String]
|
| openItems [`[FilterTypes]`](/api-documentation/api-reference/api--application/types/enums/filter-types.md) | Filter for items that are currently open or active | |
| conditionalFilters [`[ConditionalFilters]`](/api-documentation/api-reference/api--application/types/inputs/conditional-filters.md) | Conditional filters for advanced issue filtering | condition ConditionType
fieldName FilterTypes
values \[String]
greaterThan Float
lessThan Float
|
| exportsOptions [`IssuesExportOptions`](/api-documentation/api-reference/api--issue/types/inputs/issues-export-options.md) | Export options for disappeared issues data | flattenAgg Boolean
isDemoEnabled Boolean
name String
columns \[IssuesExportColumn]
rowsLimit Int
|
| restrictToCategories `[Int]` | Restricts results to specific security categories | |
| topLevelSearch `String` | Top level search value for the disappeared issues to search by Issue Name, CVE, or Application Name | |
| topOffset `Int` | Top offset for advanced pagination | |
| issueId `String` | Specific issue identifier for focused retrieval | |
| scrollDirection `String` | Direction for scrolling through results | |
| cursorValue `String` | A value returned by the API that represents the position of the last item in the previous page. Use this value to paginate efficiently through the results. Pass the cursorValue from the previous API response to fetch the next page of results. If omitted, the API returns the first page. | |
### References
#### Queries using this object:
* [\ getRemovedIssues.getRemovedIssuesInput](/api-documentation/api-reference/api--issue/queries/get-removed-issues.md)
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.ox.security/api-documentation/api-reference/api--issue/types/inputs/disappeared-issues-input.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.