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: AdminGenericInterfaceErrorHandlingDefault
Define if processing should be stopped after module was executed, skipping all remaining modules or only those of the same backend.
0/1310 · 131
English Japanese Actions
Invoker filter API実行元をフィルター
Only execute error handling module for selected invokers. 選択したAPI実行元に対してのみ、エラー処理モジュールを実行します。
Error message content filter エラーメッセージコンテンツフィルター
Enter a regular expression to restrict which error messages should cause error handling module execution.
Error message subject and data (as seen in the debugger error entry) will considered for a match.
Example: Enter '^.*401 Unauthorized.*\\$' to handle only authentication related errors.
Error stage filter エラーステージフィルター
Only execute error handling module on errors that occur during specific processing stages.
Example: Handle only errors where mapping for outgoing data could not be applied.
Error code エラーコード
An error identifier for this error handling module. このエラー処理モジュールのエラー識別子
This identifier will be available in XSLT-Mapping and shown in debugger output.
Error message エラーメッセージ
An error explanation for this error handling module. このエラー処理モジュールのエラーの説明
This message will be available in XSLT-Mapping and shown in debugger output. このメッセージは、XSLT-Mapping画面およびデバッガ出力でのみ利用可能です。
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.
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), ... 例: トリガーを 10:00 、インターバルを1分間隔にあらかじめ設定している場合に、リトライファクターを”２”とすると、次の要領でトリガーが機能します。
10:01(1分後)→10:03(１x２=2分後)→10:07(２x２=4分後)→10:15(４x２=8分後)…※以降、間隔は2倍になります
Maximum retry interval 最大リトライ間隔

Loading…

No matching activity found.
Browse all component changes

Glossary

English Japanese
No related strings found in the glossary.

String information

Source string description
Template: AdminGenericInterfaceErrorHandlingDefault
String age
4 years ago
Source string age
4 years ago
Translation file
i18n/otrs/otrs.ja.po, string 628