Writes to your workspace, only after you confirm

Repost the journals

Re-run the posting pipeline for the rows that were ready but never posted.

npx skills add wellapp-ai/skills --skill repost-journals
Wellapp
Did the accounting post?

Ask anything or use / for commands...

How the skill answers

Every step of the run, in order, with the card each one returns. A step that hands its work to another skill says which one.

  1. You ask

    Did the accounting post?

  2. Read the posting gap, then re-run the pipeline for the rows that are readySkill usedrepost-journals
  3. You get

    6 rows are ready to post and simply have not: 4 transactions and 2 supplier invoices, €18,240 for May. Nothing is wrong with them, the posting pipeline did not run. Re-run it and they book. It re-posts nothing already booked, so a second press is safe.

Frequently asked questions

What does re-triggering actually do?

It re-runs the same deterministic posting pipeline the system runs on its own, for the workspace's re-triggerable rows. It books nothing twice.

Why does it not let me pick an account?

A row that needs an account is not ready to post — it is a substantive blocker another step owns. This step lists only the rows that are ready.

What if Well is still processing the rows?

The read carries an in_flight_processing flag. While it is true, Well is still shaping the rows (enrichment in flight), so the skill polls and does not re-trigger until that work lands.

Ask your first question today

Connect your tools, then ask in plain language. Every answer traces back to the record behind it. Free to start.