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.
English Dutch
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
GenericInterface Invoker Event Settings for Web Service %s
Do you really want to delete all the conditions for this event?
Conditions can only operate on non-empty fields.
General Shortcuts
Comment code
Uncomment code