Execute Queue

The Execute Queue is where every action Patera sends shows up while it's in flight: replies, quotes, likes and unlikes. The header pill labelled Queue counts what's pending and what's running. Click it for the full popover.

These paths feed the same queue:

• Send Reply / Quote RT on a single AI Action row.
• Execute All on the AI Actions column header: drains every queued reply/quote at once.
• Auto Dispatch in the AUTO menu: sends drafts the moment they're ready.
• The heart on any tweet card (Live Feed, Top Performers), on a reply in the comments popout or on the Original Tweet row inside an AI Action: likes or unlikes that post.
• Auto-like: when Auto like posts is on, replying to or quoting a post also likes it. The like gets its own row. See Auto-like rows below.

Reply and quote rows share the same worker and pacing. Like and unlike rows behave differently: they fire concurrently the moment you click and never wait in the serial queue. The two kinds are detailed below.

What the header pill shows

The pill is hidden when nothing is queued. Otherwise it shows:

The inline pill shows running and pending counts. Hover for a tooltip with all three: N pending · N running · N failed. Click to open the popover.

What each row shows

Every row in the popover is one action. Reading left to right:

• Target avatar (28px, left edge): the face of the user you're acting on. Hover for "to @them".
• Status pill: pending, running, done, failed or cancelled. The current state's word is stamped in colour.
• Action type: Reply, Quote, Like or Unlike. For likes and unlikes the verb tracks state: a like reads Liking while running, Liked once done, Like if it failed; an unlike reads Unliking / Unliked / Unlike.
• Tone pill (reply/quote rows only): a small accent pill showing the tone the model used. For a Random-tone draft it shows the meta and the rolled tone joined by an arrow, for example Random → Casual. Like and unlike rows have no tone pill.
• Cancel button (top right, only while pending): removes the row before it ever runs. Like/unlike rows are never pending, so they never show Cancel.
• "to @them · as @us" line: confirms whose tweet you acted on and which of your accounts posted it.
• The reply you sent (reply/quote rows only), italicised in quotes, capped at 2 lines. Like/unlike rows carry no text, so this line is hidden for them.
• Tweet ID reference, shown as on tweet <id>: the post the row acts on.
• View tweet link. For a reply or quote it opens the newly-posted tweet once it lands. For a like or unlike no new tweet is created, so it links back to the target tweet you acted on and it shows immediately.
• Posting-account avatar (20px, right edge): the face of your account doing the posting. Hover for "as @us".

Two avatars per row tell you who you acted on and which of your accounts did it. That stays clear even when an Execute All sweep is fanning out across multiple accounts.

Auto-like rows

When Auto like posts is on, replying to or quoting a post also likes it (see the AUTO menu on AI Actions for the Before / After / Off timing). The like surfaces as its own separate Like row next to the reply/quote row with its own toast.

The like is performed inside the reply/quote call, not as a separate worker pass, so this row is created already resolved. It appears directly as Done or as Failed with Auto-like did not complete if the favourite didn't land. It never counts against your reply or analysis quota.

Status flow

Each row moves through this sequence:

pending → running → done
                  ↘ failed
pending → cancelled

This is the path for reply and quote rows. Like and unlike rows skip pending and cancelled entirely: they enter as running the moment you click, then resolve to done or failed.

• Pending: enqueued, waiting its turn. A Cancel button removes it before it ever fires. Only reply/quote rows are ever pending.
• Running: the worker has picked it up and is talking to X. At most one reply/quote row runs at a time; like/unlike rows can run concurrently alongside it (and alongside each other, across different tweets).
• Done: the action landed. Reply/quote rows get a "View tweet" link to the new tweet; like/unlike rows link back to the target. A success toast also fires with the same target avatar that's on the row.
• Failed: X (or the network) returned an error. The error message is shown inline so you don't have to hunt for it. An error toast fires.
• Cancelled: removed by you while pending. Doesn't run, doesn't count against quota.

Pacing

The serial worker drains reply and quote rows one at a time, not in parallel. Between each one a random delay is sampled. The default range is 1-3 seconds; you can configure it anywhere in 0-30 seconds in the Execute All: interval section of the Tone settings modal. This delay is a single global per-browser setting, not a per-tone value.

A solo enqueue (one Send Reply click or one auto-dispatched row) fires immediately. The delay only kicks in between reply/quote items, so a single send is instant and a bulk send is paced.

Likes and unlikes are not part of this. They fire concurrently the moment you click, never wait in the serial queue and never count against your reply or analysis quota. (Fast toggles on the same tweet are still ordered so X ends up matching the heart; different tweets stay fully concurrent.)

Why pace reply/quote at all: ten posts from the same workspace inside a single second looks like automation. The same ten posts dripped over a minute or two does not.

Toasts

Each row's completion fires a toast at the bottom of the screen:

• Reply / quote success: "Replied to @them as @us" (or "Quoted @them as @us") with the target's avatar, the reply text quoted underneath, the tone pill and a "View tweet" link.
• Like / unlike success: "Liked @them as @us" (or "Unliked @them as @us") with the target's avatar and a "View tweet" link back to the target post.
• Error toast: "Post failed", "Like failed" or "Unlike failed" with the upstream error message.

When auto-like is on, a reply/quote produces two toasts: one for the reply or quote and one for the like.

Toasts are short-lived (default 5 seconds) but pause when you hover over them. The toast and the queue row tell you the same thing. The toast is the glance; the queue is the audit trail.

Clear completed

The popover header has a Clear completed button. It drops every done / failed / cancelled row and keeps anything still pending or running. Use it to tidy up after a big sweep.

When the queue persists

The queue persists across reloads. It's saved to your browser's local storage (key patera-execute-queue-v1), so closing the tab or hard-refreshing does not wipe it. When you reopen Patera in the same browser:

• Pending rows resume and run.
• Done, failed and cancelled rows come back as they were, so you keep the history until you Clear completed.
• Rows that were mid-flight (running) when the page closed are reconciled, because Patera can't see whether the request actually landed:
  • An interrupted reply or quote becomes Failed with Interrupted by page reload. X's CreateTweet isn't idempotent, so Patera will not auto-retry it: re-running could double-post. Re-send it yourself if it didn't go through.
  • An interrupted like or unlike becomes Done. Favourites are idempotent and the optimistic heart already persisted, so the row agrees with the heart you already see.

The local storage is per-browser, so a queue you build on one machine won't show up on another.

Cross-reference

• The reply/quote triggers live in AI Actions: Send Reply, Execute All and the Auto menu. Auto like posts and its Before / After / Off timing live in the same AUTO menu.
• The inter-post delay is set in the Execute All: interval section of the Tone settings modal.
• The "to @them as @us" pairing reflects multi-account posting; each row picks up the X account assigned to that action.
• Likes fire from the heart on tweet cards in the Live Feed and Top Performers and replied tweets there get a "replied" pill the second a queue row lands done.