Branch Activities Tab

The Activities tab shows all jobs and pipelines executed on a branch, including deployments, merges, validations, and system actions, with detailed logs for tracking progress and outcomes.

The Activities tab provides a complete record of branch-level operations. Every job or pipeline run is tracked here, giving teams visibility into what actions were taken, who initiated them, and whether they succeeded or failed.

Jobs

Jobs represent individual actions executed on the branch. Supported job types include:

• Commit to Branch – saving component changes to the branch.

• Merge – merging changes from another branch.

• Deploy – deploying branch components into a target connection.

• Validate – checking changes against a target without deploying.

• Pre Deploy Fix Search – analyzing potential deployment issues before execution.

• Search Conflicts – detecting conflicts between branch and target org.

• Rollback – undoing a previous deployment.

• Webhook – external event triggers.

• Overwrite Protection – preventing overwriting of changes by validating latest source.

Each job entry displays its status, start and end time, duration, and the user or system that triggered it.

Pipelines

The Pipelines section tracks pipeline runs associated with the branch. Each pipeline run shows:

• Pipeline Name – such as QA Team Pipeline or ReleaseBranch Pipeline.

• Status – completed successfully or failed with an exception.

• Execution Time – start and end timestamps.

• Duration – total run time.

This allows you to validate automated workflows and monitor release progress across multiple environments.

Status Types and Use Cases

Every job or pipeline shows one of the following statuses:

• In Progress – the operation is currently running (e.g., a deployment or validation in progress).

• Aborted – the operation was manually aborted by opening the activity and clicking abort (e.g., if the wrong connection was chosen).

• Completed – the operation finished successfully with no errors (e.g., successful merge or deploy).

• Exception – an error occurred and logs should be reviewed to identify and resolve the issue (e.g., component dependency failure during deployment).

• Action Required – the pipeline requires manual steps before it can continue (e.g., waiting for user approval in a release pipeline).

Job Details

Clicking into a job opens its detailed log view. The left side shows metadata like connection, status, user, and timestamps. The right side shows step-by-step execution logs such as component retrieval, backup creation, manifest preparation, deployment start and completion, and number of components deployed. This provides full transparency into what happened during the job.

Best Practices

• Use Search Conflicts before merging or deploying to avoid overwriting changes.

• Run Validate to confirm success before actual deployment.

• Abort jobs quickly if incorrect branches or connections were selected.

• Track pipeline status carefully, especially when action is required for manual approvals.

• Review logs after any exception to troubleshoot issues quickly.