Skip to content
Lemma

Lemma Help Center

Find the next step

Enter at least two characters

Search by the job or state you see.

Results are grouped by guide, so each article is one keyboard stop.

Truth and recovery

Use the Audit log

Read a read-only timeline of committed controls and provider-confirmed LinkedIn actions.

In this collection
On this page

Open Settings → Audit log.

The Audit log combines two proof grades:

  • Control committed — Lemma committed a Sender, Do not contact, Mission, or approval-policy change.
  • Provider confirmed — a LinkedIn receipt confirms an invitation, message, or withdrawal.

Events covered

The current log can include:

  • Sender connected, reconnected, replaced, paused, or resumed;
  • Sender daily target or active-window changes;
  • Do not contact added or removed;
  • Mission launched, paused, resumed, completed, or archived;
  • Mission approval or execution-mode changes;
  • LinkedIn work held or resumed;
  • LinkedIn invitation sent, message sent, or invitation withdrawn.

Read an entry

Each entry shows:

  • a human-readable action;
  • proof grade;
  • Operator or System actor;
  • UTC timestamp;
  • a short summary;
  • links or short IDs for the Mission, Lead, Sender, task, or provider receipt when available.
Use the proof grade

A committed control proves Lemma accepted the control change. It does not prove LinkedIn performed an action. Use a Provider confirmed entry or the Sequence history for that claim.

Filter the log

Filter by Action, exact Mission ID, exact Lead ID, From, and To dates. Choose Apply filters. Use Load 50 more for the next page.

If a UUID filter is invalid, return to the unfiltered Audit log and copy the ID from the relevant Mission or Lead link.

Unavailable or stale data

When Lemma cannot verify the complete audit union, it does not present a partial result as empty:

  • Unavailable shows no partial history and offers Retry.
  • Stale preserves the last verified page, labels it stale, and disables further paging until refresh succeeds.

Next action

Use Execution evidence to interpret the entry, or Contact Support when an expected event is missing.