Retry Limits Using REST API
On This Page
Overview
When issues occur during transfer, DryvIQ will categorize the issues based on the error and flag for manual remediation. This allows you to easily identify areas for review. DryvIQ will retry an item three times by default. You can change the retry limit for different error messages.Â
Format
{ "name": "Zips File Errors", "description": "Files with extension *.zip that failed.", "filter": { "rules": [ { "text": "[audit_type] >= 5000", "type": "filter_context" }, { "text": "*.zip", "targets": [ "item" ], "type": "filter_pattern" } ] }, "action": "retry", "max_retry": 3, "level": "error", "priority": 10000 }
Parameters
Parameter | Description | Required |
---|---|---|
name | The name of the category | Required |
description | An optional description for the category | Optional |
filter | The criteria used to match an item to the category. There are two kinds:
| Required |
action | This identifies the action to take. There are three option:
| Required |
max_retry | The number of retries to attempt before the item is ignored. The default value is 3 | Optional |
Filter by Context MetadataÂ
The table below lists your options for filtering based on context metadata.Â
Name | Type | Description | Example | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
audit_type | Integer | The audit type:
| The example below includes any items with unknown errors.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
audit_level | Integer | The audit level:
| The example below includes any items with warnings.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
message | String | The error message that cause of the item failure. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
event_type | String | The event source of the original transfer operation:
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
hresult | String | The system hresult code, if the error was generated by an exception | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
exception | String | The exception type, if the error was generated by an exception |
Filter by Name PatternÂ
You can also match categories by file path pattern. The example below includes any container (e.g. directory) with "secret" as any part of its name.
{ Â Â Â Â ... Â Â Â "filter": { Â Â Â Â "rules": [{ Â Â Â Â Â Â Â Â Â Â Â Â "text":Â "*secret*", Â Â Â Â Â Â Â Â Â Â Â Â "targets": [ Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â "container" Â Â Â Â Â Â ], Â Â Â Â Â Â "type":Â "filter_pattern" Â Â Â Â Â Â Â Â }], Â Â } Â Â Â Â ... }