The translation is temporarily closed for contributions due to maintenance, please come back later.
The translation was automatically locked due to following alerts: Could not update the repository.

Translation

English Template: AdminGenericInterfaceErrorHandlingRequestRetry
If a request returns an error even after a first retry, define if subsequent retries are triggered using the same interval or in increasing intervals.
46/1500 · 150
English Chinese (Simplified) Actions
An error explanation for this error handling module. 该错误处理模块的错误说明。
This message will be available in XSLT-Mapping and shown in debugger output. 此消息将在XSLT映射中可用，并在调试器输出中显示。
Define if processing should be stopped after module was executed, skipping all remaining modules or only those of the same backend. 定义在执行模块后是否应该停止处理，跳过所有剩余的模块，或者只跳过同一个后端的模块。
Default behavior is to resume, processing the next module. 默认行为是恢复，处理下一个模块。
This module allows to configure scheduled retries for failed requests. 此模块允许配置失败请求的安排重试次数。
Default behavior of GenericInterface web services is to send each request exactly once and not to reschedule after errors. 通用接口Web服务的默认行为是每个请求仅发送一次，在错误后不再安排发送。
If more than one module capable of scheduling a retry is executed for an individual request, the module executed last is authoritative and determines if a retry is scheduled. 如果针对个别请求执行多个能够计划重试的模块，则最后执行的模块是权威性的，并确定是否安排重试。
Request retry options 请求重试选项
Retry options are applied when requests cause error handling module execution (based on processing options). 当请求导致错误处理模块执行（基于处理选项）时，将应用重试选项。
Schedule retry 安排重试
Should requests causing an error be triggered again at a later time? 是否应该在稍后的时间再次触发引起错误的请求？
Initial retry interval 初始重试间隔
Interval after which to trigger the first retry. 间隔之后触发第一次重试。
Note: This and all further retry intervals are based on the error handling module execution time for the initial request. 注意：本次及后期所有的重试间隔都基于初始请求的错误处理模块的执行时间。
Factor for further retries 进一步重试的因子
If a request returns an error even after a first retry, define if subsequent retries are triggered using the same interval or in increasing intervals. 如果请求在第一次重试后仍然返回错误，定义是使用相同的间隔时间还是增加间隔时间来触发后续重试。
Example: If a request is initially triggered at 10:00 with initial interval at '1 minute' and retry factor at '2', retries would be triggered at 10:01 (1 minute), 10:03 (2*1=2 minutes), 10:07 (2*2=4 minutes), 10:15 (2*4=8 minutes), ... 示例：如果一个请求的初始间隔为“1分钟”、重试因子为“2”，初始触发在10:00，重试将触发在10:01（1分钟），10:03（2 * 1 = 2 分钟），10:07（2 * 2 = 4分钟），10:15（2 * 4 = 8分钟），...
Maximum retry interval 最大重试间隔
If a retry interval factor of '1.5' or '2' is selected, undesirably long intervals can be prevented by defining the largest interval allowed. 如果选择重试间隔因子“1.5”或“2”，则可以通过定义允许的最大间隔时间来防止不期望的长间隔时间。
Intervals calculated to exceed the maximum retry interval will then automatically be shortened accordingly. 计算出超过最大重试间隔的间隔将自动相应缩短。
Example: If a request is initially triggered at 10:00 with initial interval at '1 minute', retry factor at '2' and maximum interval at '5 minutes', retries would be triggered at 10:01 (1 minute), 10:03 (2 minutes), 10:07 (4 minutes), 10:12 (8=>5 minutes), 10:17, ... 示例：示例：如果一个请求的初始时间间隔为“1分钟”，重试因子为“2”，最大间隔为“5分钟”，初始触发在10:00，重试将触发在10:01（1分钟），10 ：03（2分钟），10:07（4分钟），10:12（8 => 5分钟），10:17，...
Maximum retry count 最大重试次数
Maximum number of retries before a failing request is discarded, not counting the initial request. 失败请求被丢弃之前的最大重试次数，不计入初始请求。
Example: If a request is initially triggered at 10:00 with initial interval at '1 minute', retry factor at '2' and maximum retry count at '2', retries would be triggered at 10:01 and 10:02 only. 示例：如果一个请求的初始时间间隔为“1分钟”，重试因子为“2”，最大重试次数为“2”，初始触发在10:00，将仅在10:01和10:03触发重试。
Note: Maximum retry count might not be reached if a maximum retry period is configured as well and reached earlier. 注意：如果配置了最大重试时间并且较早到达，则可能无法达到最大重试次数。
This field must be empty or contain a positive number. 此字段必须为空或包含正数。
Maximum retry period 最大重试时间
Maximum period of time for retries of failing requests before they are discarded (based on the error handling module execution time for the initial request). 在丢弃失败请求之前重试的最长时间（基于初始请求的错误处理模块执行时间）。
Retries that would normally be triggered after maximum period is elapsed (according to retry interval calculation) will automatically be triggered at maximum period exactly. 在最大时间段之后正常触发的重试（根据重试间隔计算）将在最大时间段到达时自动触发一次。
Example: If a request is initially triggered at 10:00 with initial interval at '1 minute', retry factor at '2' and maximum retry period at '30 minutes', retries would be triggered at 10:01, 10:03, 10:07, 10:15 and finally at 10:31=>10:30. 示例：如果一个请求的初始间隔为“1分钟”、重试因子为“2”、最大重试时间为“30分钟”，初始触发在10:00，重试将触发在10:01、10:03、10:07、10:15，最后在10：31 => 10:30触发一次。
Note: Maximum retry period might not be reached if a maximum retry count is configured as well and reached earlier. 注意：如果配置了最大重试次数并且较早到达，则可能无法达到最大重试时间。

Loading…

No matching activity found.
Browse all component changes

Glossary

English Chinese (Simplified)
No related strings found in the glossary.

String information

Source string description
Template: AdminGenericInterfaceErrorHandlingRequestRetry
String age
4 years ago
Source string age
4 years ago
Translation file
i18n/otrs/otrs.zh_CN.po, string 641