Version History Issues

Fix SharePoint Check-In Comments Missing from Version History

Tauseeq MagsiTauseeq Magsi Oct 26, 2026 870 views

Question details

SharePoint document check-in comments are disappearing from the version history, causing incomplete auditing logs.

Fix SharePoint Check-In Comments Missing from Version History
Product
Microsoft SharePoint / Power Automate
Device & OS
not provided
Scenario
Tracking document history and auditing versions using SharePoint alongside Power Automate flows.
Observed behavior
Check-in comments initially appear but disappear when Power Automate performs a subsequent check-out/check-in operation on the document.
Before you start

Review your active Power Automate flows connected to the affected SharePoint document library to identify any automated check-out or check-in steps.

Solution 1Recommended

Add a Delay Action in Your Power Automate Flow

Prevent Power Automate from overwriting or deleting check-in comments during fast sequential check-out and check-in operations.

When a flow performs a secondary check-out and check-in immediately after a user adds a comment, the rapid succession can cause SharePoint to overwrite or drop the original comment metadata.

1
Edit the Power Automate Flow

Open Power Automate, locate the flow linked to your SharePoint document library, and click 'Edit'.

2
Locate the Secondary Check-out

Scroll through your workflow to find the step where the flow checks out the document for a second time.

3
Insert a Delay Action

Click the '+' icon right before the check-out step, select 'Add an action', and search for 'Delay'.

4
Configure the Delay Timer

Set the Delay action duration to at least 1 minute to give SharePoint enough time to register the initial comment.

5
Save and Test

Save your flow and perform a test check-in on a document to verify that the comment is now retained in the version history.

Add a Delay Action in Your Power Automate Flow
Auditing Restored: Adding this brief pause gives SharePoint the necessary time to fully commit the initial version history metadata, ensuring your audit trails remain intact.
Free Microsoft Office alternative

Try WPS Office for Seamless Document Collaboration

While troubleshooting complex SharePoint and Power Automate issues, consider using WPS Office for your daily document management. It is a highly compatible, free, and lightweight suite that handles standard document formats with ease, simplifying team collaboration without the need for complex automation.

  1. 1. Download WPS Office: Visit the official WPS Office website and download the free installation package for your operating system.
  2. 2. Install the Software: Run the installer and follow the on-screen instructions to quickly set up the office suite.
  3. 3. Manage Your Documents: Open your files directly in WPS Office to enjoy reliable version history tracking and seamless editing.
Fully compatible with Microsoft Word, Excel, and PowerPoint formats.Comprehensive version history tracking for safe and transparent document editing.Built-in cloud collaboration and file sharing without complex automation setups.Lightweight design ensuring fast installation and smooth performance.
microsoft office alternative - wps office

Frequently Asked Questions

Why do SharePoint check-in comments suddenly disappear?

Comments often disappear when automated workflows, such as Power Automate, check out and check in the document immediately after a user does. The fast secondary check-in operation can overwrite the initial check-in data.

Can I recover a check-in comment that was deleted by Power Automate?

Unfortunately, if the workflow overwrites the check-in data without retaining the original comment, the comment is usually permanently lost from the version history. You will need to prevent it from happening on future documents by adding a delay to your flow.

Is there a workaround to show all comments for auditing purposes?

Some users attempt to display the most recent comment using custom columns, but this is typically insufficient for proper auditing, which requires a complete, step-by-step version history. Fixing the automated flow is the best approach to maintain compliant audit logs.