Activity Execution Flow
Last updated on
Activities execute based on their dependencies and type.
Activity Execution
Pipeline Activities
Pipeline activities (automated activities) execute by:
- Triggering the associated Harness pipeline
- Passing activity inputs to the pipeline
- Tracking pipeline execution status
- Capturing pipeline outputs
Manual Activities
Manual activities execute by:
- Going into an "on hold" or "waiting for input" state
- Sending notifications to assigned users
- Waiting for users to record their inputs and finalize them
- Completing once user provides sign-off or input
Subprocess Activities
Subprocess activities execute by:
- Invoking the nested process
- Executing the subprocess phases and activities
- Propagating status back to the parent process
Dependencies
Activities execute based on their dependencies:
- Activities wait for their dependencies to complete
- Dependencies can be configured between activities within a phase
- Dependencies control the execution order