Conga Product Documentation

Welcome to the new doc site. Some of your old bookmarks will no longer work. Please use the search bar to find your desired topic.

Activities

A workflow activity contains instructions for the workflow to process.

Activities can involve manipulating records, waiting for a specific time, or logging events. Workflow conditions determine if an activity will be performed. You can add, remove, or rearrange activities, and transitions can be created between them.

Sample activity: This activity sends an email to designated recipients.



Workflows execute activities under the context of the currently logged-in user or the system user, depending on the trigger type. There are two trigger types available:

  1. Record Trigger: If a workflow is started from a record operation, activities run under the user session that performed the operation.
  2. Schedule Trigger: For workflows initiated by schedules or timers, activities run under the system user.

Refer to the subtopics for core activities available in the system.

Activity Execution Limits and Loop Detection

The system controls how many times an activity can run and ensure workflows do not get stuck in endless loops. Enhanced loop detection automatically applies to activities that are configured to run in a loop, ensuring they do not continue indefinitely.

By default, an activity can run up to six times as part of enhanced loop detection. The system allows three runs, applies a five-second cooldown if it detects a loop, and then permits three additional runs. If the loop continues after this point, the system halts the activity and marks it as stopped.
Note:
  • The legacy loop detection mechanism, which allows up to two thousand executions, applies to Loop, Fork, and Decision activities.
  • To customize the default execution limit or to enable or disable the legacy mechanism, contact your Conga Support representative.