Manage asynchronous operations in Jitterbit Integration Studio

Introduction

This page provides guidance on managing asynchronous operations.

Manage asynchronous operations

When using the RunOperation function in its asynchronous mode, operations execute without returning control to the calling function. Use of asynchronous operations can lead to race conditions.

For example, if Operation A updates a database table and is chained to Operation B, which reads that same table (both are synchronous), no race conditions are encountered. But if Operation A is called asynchronously followed immediately by Operation B, then B may execute before A is finished.

In addition, the number of simultaneous asynchronous calls must be managed, as the number of simultaneous operations running on an agent is capped (see the private agent configuration file's [OperationEngine] section or Cloud agent groups).