Specifying the Retry options for Insightly REST API activities

Specifying the Retry parameters is one of the tasks to configure an Insightly activity. The Insightly REST API connector uses a single login session for all connections to an Insightly REST API endpoint. If a session expires, the connector automatically establishes a new session. The connector does not count the initial attempt to reacquiring the session as a retry attempt. The connector assumes the typical connector retry behavior after the initial attempt to reacquire a session fails. The retrial exceptions include 503 and 504 for this error codes.

About this task

This section contains the procedure for configuring the retry options for Insightly API activities.

Procedure

  1. Select the Retry task from the Checklist. The retry pane is displayed.
  2. Configure the retry options and timeout options for connecting to an Insightly instance, as described in the following table:
    Table 1. Retry options
    Retry Fields Description
    Wait __ seconds between each retry. Specifies the number of seconds that the Integration Appliance waits before trying to establish a connection to the Insightly instance.
    Retry __ times before failing. Specifies the retry count — the maximum number of times the Integration Appliance attempts to establish a connection to the Insightly instance before issuing an error and stopping the processing of the current orchestration job.
    Note: If you deploy an orchestration that contains the Insightly REST API activity and the Integration Appliance cannot connect to the specified Insightly instance, the Integration Appliance logs the connections errors as Warnings in the system and orchestration logs until the retry count value is reached. When the retry count is reached, the Integration Appliance logs an Error in the system and orchestration logs and stops processing the current orchestration job. For example, you set the retry count to 3, the first, second, and third connection errors appear in the system log as warnings. The Integration Appliance logs the fourth connection error as an error and stops processing the current orchestration job.
    Stop processing rest of the records of the batch if failure detected even after the configured no. of retries. Specifies that if a batch of records is sent as input to an orchestration, and if failure is detected in between, then the remaining records should be processed or not.

    For example, if the retry count is set to 3 and a batch of 5 records is sent as input to the orchestration. If, after processing the 1st record of batch, the Integration Appliance cannot connect to the specified Insightly instance even after configured number of retries i.e. 3 retry attempts, then the processing of the remaining 4 records will not be done and execution will be terminated if this option is selected.

    For the similar settings, if this option is not selected, then the remaining 4 records would be attempted to be processed.




Feedback | Notices


Timestamp icon Last updated: Wednesday, February 17, 2016


http://pic.dhe.ibm.com/infocenter/wci/v7r0m0/topic/com.ibm.wci.doc/Insightly_Specifying_Retry_options_for_Insightly_REST_API_activities.html