ENUM
TaskFailureReason
Need to keep in sync with https://github.com/veritone/edge-messages/blob/master/failure_reason.go
link GraphQL Schema definition
1 enum TaskFailureReason { 2 3 # The engine encountered an unexpected internal error. 4 5 6 # The cause of the failure could not be determined. 7 8 9 # The engine attempted to download 10 # content from a URL provided in the task payload and 11 # received a 404. 12 13 14 # The engine attempted to download 15 # content from a URL provided in the task payload and 16 # received a 401 or 403. 17 18 19 # The engine attempted to download 20 # content from a URL provided in the task payload and 21 # the download timed out 22 23 24 # The engine attempted to download 25 # content from a URL provided in the task payload and 26 # the connection was refused. 27 28 29 # The engine attempted to download content from a URL 30 # provided in the task payload an received an error. 31 32 33 # The input to the engine was incompatible with the engine 34 # requirements. For example, an input media file had an 35 # unsupported MIME type or the file was empty. 36 37 38 # An engine operation was subject to rate limiting. 39 40 41 # The engine received an authorization error from the Veritone API. 42 43 44 # The engine received an authentication error from the Veritone API using 45 # the token provided in the task payload. 46 47 48 # The engine received a "not found" error from the Veritone API on 49 # a required object. 50 51 52 # An unexpected error was received from the Veritone API, such as 53 # HTTP 500, HTTP 502, or an `internal_error` error. 54 55 56 # The engine could not write temporary files to disk for processing 57 # due to disk space full or other system error. 58 59 60 # The engine could not read from stream input for processing 61 # due to stream link broken or cannot connect to stream link 62 63 64 # The engine encountered a missing binary dependency or configuration, 65 # such as a missing executable or package or incompatible hardware. 66 67 68 # The engine encountered an operating system, hardware, or other 69 # system-level error. 70 71 72 # The engine failed to send heartbeat or Edge didn't receive it in time 73 74 75 # The engine failed to send chunk result, or Edge didn't receive it in time 76 77 78 # The error cause is known, but could not be mapped to a `TaskFailureReason` 79 # value. The `failureMessage` input field should contain details. 80 81 82 # The engine calls third party for processing and receives error 83 84 85 # The engine attempted to connect from a URL provided in the task payload and the 86 # connection was refused 87 88 89 # The engine received an authorization error from the Veritone API 90 91 92 # An unexpected error was received from the Veritone API, such as HTTP 500, HTTP 93 # 502, or an internal_error error 94 95 96 # The engine encountered an resource-level error 97 98 99 # The engine received a "not found" error from the Veritone API on a required 100 # object 101 102 103 # The engine encountered an unexpected core api error 104 105 106 # The engine encountered an unexpected bad data error 107 108 109 # The engine failed due to an scheduling error 110 111 112 # The failureReason doesn't match with any of taskFailureEnum values 113 114 }