Adding throttling controls

While adding or updating a connector configuration, as a tenant administrator, you can use throttling controls to impose rate limits for integrating with the connecting application. More specifically, the throttling controls are applied to API calls made to the connecting application's servers when a flow is run. 

Additonally, for the following connectors you can add polling limits to configure the number of records that are queried when the system triggers a flow run:

• AR System
• ITSM
• Jira

For more information about configuring polling limits, see Configuring-connectors.

You can initiate a flow on demand at any time for testing purposes. For more information, see Activating-or-enabling-flows.

To add throttling controls

1. Log in to BMC Helix Integration Studio.
2. Go to Catalog > Connectors, and select the connector.
3. Expand the connector pane at the bottom of the screen.
4. Click Throttling controls.
   
   
   
   
5. If no configurations exist for the connector, add one.

6. For a given configuration, populate at least one of the following fields (fields depend on the connecting application):

   Field name	Action
   Check Trigger Every	Select the callback interval for the flows using the connector.
   Maximum number of Records to process	Specify the maximum number of records to process. The default value is unlimited. This value applies for actions directly executed from BMC Helix Innovation Studio and flows executed by BMC Helix Integration Studio. Important: For the BMC Helix ITSM and Jira connector: By default the maximum value is set to 2000, which is the maximum limit that can be set for these connectors. If you add a number greater than 2000, only 2000 records are processed. This restriction applies only for Jira issues and does not apply for the processing of Jira comments.  During a flow run, if the number of records matching the qualification defined is greater than the maximum number defined, the additional records are polled in the next flow run. For additional details, see How throttling works when maximum number of records to process is exceeded.

   Important

   If you provide values for Check Trigger Every as well as Maximum number of Records to process, both fields are evaluated to throttle bandwidth. 

How throttling works when the maximum number of records to process is exceeded

If you specify a limited number of records in the Maximum number of Records to process field, and the actual number of available records in the source application exceeds your limit, you receive the following results after the flow run:

1. Only the specified number of records is transferred to the target application. Other available records are not transferred to the target application.
2. In the Flow Timeline, the error is displayed for such a flow run because not all available records are transferred to the target application.

For BMC Helix ITSM and Jira connectors:

1. All records with a time stamp before that of the last record of your maximum limit are transferred to the target application. 
2. Irrespective of the maximum limit set, if all the polled records have the same time stamp, all the records with the same time stamp are processed, and additional records are polled.
3. The last run time stamp of the flow is updated to the last record that is processed.
4. The next flow run is executed for records with the time stamp later than the last record processed.