Public run log

LinkedIn posting agent run log

Every run this agent has on record, newest first. Open a record to read the steps, where the record comes from, and what happened when something needed a person.

From the agent’s own recordsRead-only. Reconstructed from one record per posted row of the LinkedIn topic calendar and the commit that flipped it (Workflows/linkedin-post/geo-topics.md), as of Oct 10, 2026. The calendar does not record failed runs: a failed run leaves its row pending and the next run retries the same topic. The numbers below are counted from the records shown.
8Runs on record
8SucceededAll published as they ran
0FailedNot recorded by the calendar
0Needs attention
Status
Date
Oct 9, 202617:04Day 8 · Owned vs. earned vs. competitor-owned sourcesLive on the company page. The image step was in the workflow by then; the calendar does not record whether it attached.SucceededPost publishedNo one needed for this run

Steps

  1. DonePicked Day 8, the first row still marked pending
  2. DoneWrote the post to the workflow’s rules: hook first, no links, no dashes, hashtags last
  3. DoneChrome reachable and signed in; published from the company page composer
  4. DoneMarked Day 8 posted and pushed the calendar

How it was handled

No stop in this run: the row is marked posted, which the workflow only does after the publish step succeeded.

Next step

None. The record shows that the post went out, not how it performed.

Where this record comes from

Workflows/linkedin-post/geo-topics.md · commit dea25e5e

Company page

Oct 8, 202617:04Day 7 · How LLMs actually decide which brand to citeLive on the company page. The image step was in the workflow by then; the calendar does not record whether it attached.SucceededPost publishedNo one needed for this run

Steps

  1. DonePicked Day 7, the first row still marked pending
  2. DoneWrote the post to the workflow’s rules: hook first, no links, no dashes, hashtags last
  3. DoneChrome reachable and signed in; published from the company page composer
  4. DoneMarked Day 7 posted and pushed the calendar

How it was handled

No stop in this run: the row is marked posted, which the workflow only does after the publish step succeeded.

Next step

None. The record shows that the post went out, not how it performed.

Where this record comes from

Workflows/linkedin-post/geo-topics.md · commit 47c02ea2

Company page

1 day with no run on record

Oct 6, 202623:04Day 6 · Why a great website can still be invisible to AILive on the company page. The image step was in the workflow by then; the calendar does not record whether it attached.SucceededPost publishedNo one needed for this run

Steps

  1. DonePicked Day 6, the first row still marked pending
  2. DoneWrote the post to the workflow’s rules: hook first, no links, no dashes, hashtags last
  3. DoneChrome reachable and signed in; published from the company page composer
  4. DoneMarked Day 6 posted and pushed the calendar

How it was handled

No stop in this run: the row is marked posted, which the workflow only does after the publish step succeeded.

Next step

None. The record shows that the post went out, not how it performed.

Where this record comes from

Workflows/linkedin-post/geo-topics.md · commit b6a16e7b

Company page

Oct 6, 202617:04Day 5 · The four engines that matter, and how each sources differentlyLive on the company page. The image step was in the workflow by then; the calendar does not record whether it attached.SucceededPost publishedNo one needed for this run

Steps

  1. DonePicked Day 5, the first row still marked pending
  2. DoneWrote the post to the workflow’s rules: hook first, no links, no dashes, hashtags last
  3. DoneChrome reachable and signed in; published from the company page composer
  4. DoneMarked Day 5 posted and pushed the calendar

How it was handled

No stop in this run: the row is marked posted, which the workflow only does after the publish step succeeded.

Next step

None. The record shows that the post went out, not how it performed.

Where this record comes from

Workflows/linkedin-post/geo-topics.md · commit 06d1f10a

Company page

1 day with no run on record

Oct 4, 202617:04Day 4 · Why "ranking #1" doesn’t mean what it used toLive on the company page. The publishing script does not capture the permalink.SucceededPost publishedNo one needed for this run

Steps

  1. DonePicked Day 4, the first row still marked pending
  2. DoneWrote the post to the workflow’s rules: hook first, no links, no dashes, hashtags last
  3. DoneChrome reachable and signed in; published from the company page composer
  4. DoneMarked Day 4 posted and pushed the calendar

How it was handled

No stop in this run: the row is marked posted, which the workflow only does after the publish step succeeded.

Next step

None. The record shows that the post went out, not how it performed.

Where this record comes from

Workflows/linkedin-post/geo-topics.md · commit c7ce0253

Company page

Oct 3, 202617:04Day 3 · Mention Rate vs. Recommendation Rate, the metric most brands get wrongLive on the company page. The publishing script does not capture the permalink.SucceededPost publishedNo one needed for this run

Steps

  1. DonePicked Day 3, the first row still marked pending
  2. DoneWrote the post to the workflow’s rules: hook first, no links, no dashes, hashtags last
  3. DoneChrome reachable and signed in; published from the company page composer
  4. DoneMarked Day 3 posted and pushed the calendar

How it was handled

No stop in this run: the row is marked posted, which the workflow only does after the publish step succeeded.

Next step

None. The record shows that the post went out, not how it performed.

Where this record comes from

Workflows/linkedin-post/geo-topics.md · commit a5757cb5

Company page

Oct 2, 202617:05Day 2 · Why buyers now ask ChatGPT/Perplexity instead of Googling "best X"Live on the company page. The publishing script does not capture the permalink.SucceededPost publishedNo one needed for this run

Steps

  1. DonePicked Day 2, the first row still marked pending
  2. DoneWrote the post to the workflow’s rules: hook first, no links, no dashes, hashtags last
  3. DoneChrome reachable and signed in; published from the company page composer
  4. DoneMarked Day 2 posted and pushed the calendar

How it was handled

No stop in this run: the row is marked posted, which the workflow only does after the publish step succeeded.

Next step

None. The record shows that the post went out, not how it performed.

Where this record comes from

Workflows/linkedin-post/geo-topics.md · commit 307728d5

Company page

5 days with no run on record

Sep 26, 2026Day 1 · What GEO is, and how it differs from SEOLive on the company page. The publishing script does not capture the permalink.SucceededPost publishedNo one needed for this run

Steps

  1. DonePicked Day 1, the first row still marked pending
  2. DoneWrote the post to the workflow’s rules: hook first, no links, no dashes, hashtags last
  3. DoneChrome reachable and signed in; published from the company page composer
  4. DoneMarked Day 1 posted and pushed the calendar

How it was handled

No stop in this run: the row is marked posted, which the workflow only does after the publish step succeeded.

Next step

None. The record shows that the post went out, not how it performed.

Where this record comes from

Workflows/linkedin-post/geo-topics.md · commit 5878c80a · Already marked posted in the commit that created the calendar, so there is no commit of its own.

Company page

No runs match these filters

There are no runs of the LinkedIn posting agent with that status in that date range. Try a wider range or another status.

Succeeded

The task finished. The record says which: a post published, or a draft written.

Failed

The run stopped. The record says where, why, and what happens next.

Needs attention

The run is waiting on a person: a sign-in, a challenge to solve, or a closing to rewrite.

“Succeeded” means the task in the record finished, and the record says which: a post published, or a draft written. It does not measure reach, leads or revenue. Records never include private messages or personal details of people outside the team. Times are US Eastern, from the commit that wrote the record.