What action can not be performed in Copado after a merge conflict is detected?

Creating a Documentation Record cannot be performed in Copado after a merge conflict is detected because the focus during a merge conflict is primarily on resolving the conflicting changes. When a conflict arises, the workflow is directed towards addressing the discrepancies in the code or metadata that cannot automatically merge.

The other actions, such as continuing to promotion, reviewing merge conflicts, and resolving the conflict, are directly related to handling the merge conflict. Continuing the promotion makes sense only after the conflict has been resolved, while reviewing the conflicts enables developers to understand the issues that need addressing. Therefore, amidst a merge conflict, priority must be given to resolving those issues before progressing to documentation or other tasks.