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.

Source string Source string

238/10000 · 238
English Actions
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), ...
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.
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, ...
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.
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.
Note: Maximum retry period might not be reached if a maximum retry count is configured as well and reached earlier.
Add Invoker
Edit Invoker
Do you really want to delete this invoker?
Invoker Details
The name is typically used to call up an operation of a remote web service.
Invoker backend
This OTRS invoker backend module will be called to prepare the data to be sent to the remote system, and to process its response data.
Mapping for outgoing request data
Configure
The data from the invoker of OTRS will be processed by this mapping, to transform it to the kind of data the remote system expects.
Mapping for incoming response data
The response data will be processed by this mapping, to transform it to the kind of data the invoker of OTRS expects.
Asynchronous
Condition

Loading…

User avatar None

New source string

OTRS / i18n — English

New source string 4 years ago
Browse all component changes

Things to check

Multiple failing checks

Following checks are failing:
Zero-width space: Italian, Polish

Reset

Glossary

English English
No related strings found in the glossary.

String information

Source string description
Template: AdminGenericInterfaceErrorHandlingRequestRetry
Flags
read-only
String age
4 years ago
Source string age
4 years ago
Translation file
string 655