TwentyDEV icon

TwentyDEV

Consume the Twenty API
Join our community

Actions252

Overview

This node operation, Find Workflow Run Duplicates, is designed to identify duplicate workflow runs based on specified criteria. It allows users to query for workflow runs that match certain data attributes or IDs and retrieve information about these duplicates. This can be particularly useful in scenarios where workflows might be triggered multiple times with the same input or under similar conditions, and you want to detect or handle such repetitions to avoid redundant processing or to audit workflow executions.

Practical examples include:

  • Detecting repeated workflow runs caused by accidental re-submissions.
  • Auditing workflow executions to find duplicates for cleanup or reporting.
  • Preventing duplicate processing in automation pipelines by identifying existing runs with matching parameters.

Properties

Name Meaning
Depth Determines how much related nested information to include in the response:
- 0: Only the primary workflow run object.
- 1: Primary object plus its directly related objects.
- 2: Primary object, its related objects, and their related objects.
Data JSON array specifying the data attributes to match against when searching for duplicate workflow runs. Each object in the array represents a set of key-value pairs (e.g., status, name) used as filters for finding duplicates.
Ids JSON array of workflow run IDs to specifically check for duplicates. Can be used to limit the search to particular workflow runs by their unique identifiers.

Output

The node outputs JSON data representing the found duplicate workflow runs. The structure includes the workflow run objects along with related nested objects depending on the selected depth level. The output contains all relevant details of each duplicate run, such as status, name, and any other properties returned by the API.

If binary data were involved, it would typically represent attachments or files related to the workflow runs, but this operation focuses on JSON data only.

Dependencies

  • Requires an API key credential to authenticate requests to the external Twenty API service.
  • The node uses the Twenty API base URL configured via credentials.
  • No additional environment variables are explicitly required beyond standard API authentication setup.

Troubleshooting

  • Invalid JSON in Data or Ids: Since data and ids inputs expect JSON arrays, malformed JSON will cause errors. Ensure valid JSON formatting.
  • Authentication Errors: Missing or incorrect API credentials will result in authorization failures. Verify that the API key credential is correctly configured.
  • No Duplicates Found: If no duplicates are returned, verify that the filter criteria in data or ids accurately reflect existing workflow runs.
  • Depth Parameter Misuse: Setting an unsupported depth value may lead to incomplete or excessive data. Use only 0, 1, or 2 as defined.

Links and References

Discussion