Error and Retry

Pipeline error

The following errors occurs when pipeline is executed.

Compile error

The compile error is an error that occurs when the pipeline is set and saved. The pipeline cannot be started while the compile error has occurred.

When the pipeline is saved, contents of error is displayed in the message area under the coordinator. Most errors occurred when saving it without inputting a necessary field, so confirm settings contents please.

Error when sensor is executed

The error occurs when the sensor is executed while reading data in the sensor stage after the pipeline is started. Occurred error is chiefly output to pipeline log of each pipeline, and a part of contents is output to engine log.

There are a little difference between schedule type and direct type, main reasons are as follows.

When the error occurred in sensor, former data is not usually deleted. It is possible to restart and recover it by correcting and saving the definition of the pipeline because of the mistake of sensor settings. If it is schedule type action and input same data to recover when execute next time, if it is direct type action and input same data to recover when request next time. However, there is a case that cannot be recovered by this method according to the sensor, too. For details please see help of action used.

There is no retrying mechanism when the error occurs in the sensor.

Error when filter is executed

The error doesn't usually occur while executing the filter because data conversion is a center. However, it is necessary to note type conversion fail and actions that access external resource and external server.

Occurred error is chiefly output to pipeline log of each pipeline, and a part of contents is output to engine log.

It can be retried manually, automatically when error occurred in filter. To retry automatically, it is necessary to specify retrying times, retrying standby time in pipeline settings in advance. It is possible to execute again from the request monitor to retry manually from where error has occurred.

Error when joint is executed

Because data is often delivered to an external resource and an external server in joint, the possibility that the error occurs because of an external factor is high. Therefore, the retrying mechanism is provided in pipeline service.

Occurred error is chiefly output to pipeline log of each pipeline, and a part of contents is output to engine log.

In joint also provides two retrying mechanisms, automatic retrying and manual retrying same as filter. The method is the same as the case of the filter. The method is the same as the case of the filter. Set pipeline to retry. Execute again from the request monitor to retry manually.

Error of pipeline service

Besides this, error of the pipeline service might occur. Because resource shortage becomes major reason, such as memory shortage or disk capacity shortage, we will recommend you to monitor status by using operation monitor tool that system monitor of pipeline service or Operating System or the third party provides.

Occurred error is chiefly output to engine log and system log. Especially when the error of memory shortage occurs, and it might influence processing afterwards, we recommend that you plan on enhancing resources after restart the pipeline service.

Error when action is executed

How to operate the pipeline afterwards when the error occurs during action is being executed, wes summarized the following table.

Which "Processing when errors occurred" is processed when various errors occur in action, contents of "Processing when errors occurred" in the table below is described in help of "Error processing" of each action.

Processing when errors occurred Explanation
End Pipeline is end.
Retry Retry automatically.
However, automatic retrying is not set in pipeline settings it will be executed as"End because of error".
End because of error It is error because retrying is not processed.
In pipeline settings, if set "Save queue when error occurs" to "yes", request status changes to "Manually retry waiting",if set to "no", request status will be "Error".
To the next action End action execution where the error occurs, and move to next action.
Processing continuation Continue action processing where the error occurs.
Example：Get property value in case of failure, use the specified value and continue processing; in the way of data records processing where the error occurred, skip the record and continue processing the next record.
How processing is continued according to the action.

▲ Top