What are runs

In the Getint platform, a "Run" is a critical operation in the synchronization process between connected tools. Here’s an extended explanation, including the recording and logging of each Run.

Initiating Synchronization:

A Run occurs when Getint sends API requests to connected collaboration tools. These requests aim to gather data on all newly created items and their respective fields, as well as any recent updates, as defined in the integration setup.

Detection and Integration of Changes:

Getint actively searches for new items or changes in existing items during a Run. Detected changes are then integrated, ensuring data across the tools remains synchronized and current.

Handling Concurrent Changes:

Getint effectively merges data when changes occur simultaneously in the same field across integrated tools. This merging mechanism is crucial for preserving all updates and preventing data loss.

Recording and Logging of Runs:

Every Run is meticulously recorded and logged within Getint. This means that users have the ability to review and analyze the actions taken during each Run.

The logs provide valuable insights into the outcomes of each synchronization process. They are an essential tool for users to easily identify and understand any errors or discrepancies that may occur.

Ensuring Data Integrity and Continuity:

Regular Runs are essential for maintaining data integrity and continuity across different platforms. They ensure that all integrated systems reflect the latest and most accurate data.

In summary, a Run in Getint is not only a process of querying and integrating data but also involves a comprehensive recording and logging mechanism. This feature allows users to monitor, analyze, and troubleshoot the synchronization process, ensuring transparency and control over data integration across their collaboration tools.