Currently, there is no built-in functionality to track when a Merge Action (Document or Email Merge) is executed manually, including who ran it and when it was run.
This makes it difficult for administrators to:
Audit merge activity for compliance and governance purposes
Identify which user manually executed a merge
Distinguish between scheduled merges and manually triggered merges
Investigate unexpected document/email activity
Maintain accountability in environments with multiple users
While scheduled job executions are logged through scheduler logs, manual executions (including test runs and button-triggered merges) are not captured in a reportable, user-facing log.