A LinkedIn Repost Roster Returned After Evidence Quarantine: Reconcile Every Amplifier

A returned roster is usable only after you prove which rows survived quarantine unchanged. Start from the quarantined snapshot, load the restored snapshot beside it, and compare stable identifiers before anyone takes an action.

The working key is the stable profile ID plus the repost ID. Add the source-post binding, action state, decision, reviewer, and timestamps. That gives you a record that can explain why one row was released while the row beside it stayed on hold.

LinkedIn's Posts API identifies posts with share or UGC post URNs. For a reshare, the documented reshare context records a parent post and derives a root post from that parent. LinkedIn / Microsoft Learn documents those fields.

• Freeze the quarantined roster as the prior snapshot. Do not overwrite it.
• Export the restored roster with its capture timestamp and source system.
• Create one ledger row for every prior or restored record, including rows that will remain on hold.

Which identifiers must match before a roster row can return?

Use identifiers that stay attached to the record, not labels that people edit. A display name, headline, job title, profile photo, or copied post text can help a reviewer inspect the row. None should decide release by itself.

For each restored row, compare the prior and restored stable profile ID, repost ID, and source-post binding. A source-post binding means the parent or root post recorded for that repost. Treat a missing identifier as incomplete evidence, not a match.

Keep a source-system reference as well. It tells the reviewer where each snapshot came from and prevents a later export from being mistaken for the quarantined baseline.

• Stable profile ID: the persistent identity field used by the roster system.
• Repost ID: the post or share identifier for the specific repost record.
• Source-post binding: the documented parent or root post connected to that repost.
• Snapshot reference: the export, query, or source record used to capture the row.

What should the positive-release ledger record?

Build the ledger before you decide which rows can return. It is a comparison table, so every release has its prior record, restored record, delta, dependent action, decision, reviewer, and timestamp in one place.

The table below is a field-level release template. Replace the placeholder values with actual records from the two snapshots. Do not create sample IDs and then treat them as evidence.

This format keeps release decisions individual. A clean row does not clear another row that has a changed source binding or a prior touch.

Which changes block reuse of an amplifier row?

Hold a row when any release field differs or cannot be verified. A change is a signal to investigate, not a reason to copy the new value into the old record.

An addition has no quarantined baseline. A removal has no restored row. A source change means the repost may now point to a different parent or root post. A duplicate touch means the dependent action may already have happened or still be pending.

LinkedIn's social-actions documentation distinguishes summaries from the underlying likes and comments and recommends checking a summary before fetching those records. Use that sequence when the duplicate check relies on social-action evidence. LinkedIn / Microsoft Learn documents the retrieval behavior.

• Added identity or repost: hold until a reviewer establishes a valid baseline.
• Removed identity or repost: close or hold the dependent action. Do not recreate the row from memory.
• Changed stable profile ID or repost ID: hold. The record is not the same row.
• Changed source-post binding: hold. Review the source post and the reason for the change.
• Duplicate completed or pending touch: hold the next action until the action history is resolved.
• Missing snapshot reference, reviewer, or timestamp: hold because the decision cannot be rechecked.

Which actions can be released individually?

Release only the dependent action attached to a row that passes every comparison. Record the decision with its reviewer and timestamp before the action enters an operating queue.

Examples of row-level decisions include retaining a record for future review or closing a stale dependent action. A reviewer may also consider the next legitimate outreach step. The ledger does not turn a repost record into an instruction to coordinate engagement.

If the record relates to company-post measurement, keep the measurement scope attached to the record. LinkedIn documents that its organizational share-statistics endpoint covers organic statistics and uses a rolling 12-month window for organization share data. LinkedIn / Microsoft Learn, April 30, 2026 documents those limits.

• Release: all three identity and binding fields match, the duplicate check is clear, and the reviewer signs the row.
• Hold: any mismatch, missing evidence, unresolved source change, or duplicate touch.
• Close: the restored record is absent and the dependent action has no valid target.

How should the roster stay inside LinkedIn's rules?

Use the roster as an audit tool. Do not use it to arrange reciprocal reposts, repeated amplification, or other activity meant to artificially increase engagement.

LinkedIn's Professional Community Policies say members must not artificially increase engagement and must not agree with others ahead of time to like or re-share content. The same policies require true identity and real, authentic information. LinkedIn sets those boundaries.