Fix scheduling and approval problems

Resolve scheduling problems: an entry stuck at Pending approval, a run that shows Failed, a Dead-lettered job, or a wrong scheduled time — all inside the internal queue, where nothing is delivered externally.

Purpose

Diagnose and clear the common reasons a schedule request stalls at Pending approval or a run ends Failed or Dead-lettered in the durable internal queue. External publishing does not exist in this release, so none of these problems involve an outside network.

Who this is for

Creators and admins whose scheduled entry stalled in approval or whose run shows Failed or Dead-lettered.

Prerequisites

Access to the affected entry and its project.
The second human responsible for approvals, if the entry is waiting on one.
The entry's recorded status label and any customer-safe error shown on it.

Steps

Open the entry and read its current label: Pending approval, Approved · scheduled, Queued internally, Completed internally · not delivered, Failed, or Dead-lettered.
For an entry stuck at Pending approval, confirm a second human with approver rights is available, and remind them in the Approval Queue.
For a wrong time, check the scheduled time and timezone recorded on the entry, then reschedule it.
For a Failed run, read the customer-safe error recorded on the entry; the internal worker retries automatically before giving up.
For a Dead-lettered job, the durable queue has stopped retrying after repeated failures; review the recorded error and request a new schedule.
Confirm the entry's new state, and check the audit trail for what happened and who decided.

Expected result

The blocker is identified from the entry's recorded status, and the entry is approved, rescheduled, or re-requested — every run stays recorded internally, and nothing is delivered to any external network.

Verification

The entry shows Approved · scheduled if a second human approved it.
A retried run leaves Failed and shows Queued internally, then Completed internally · not delivered.
The audit trail records each decision and state change.

If something goes wrong

An entry stays Pending approval: Only a second human can move it; confirm the approver has the required role and is available, and reassign if your workspace allows it.
A run keeps ending Failed: The internal worker retried and recorded a customer-safe error each time; read the error on the entry, fix the cause, then request a new schedule.
A job shows Dead-lettered: The durable queue stops retrying after repeated failures and keeps the record; request a new schedule once the recorded cause is addressed.
You expected the post to appear on the social network: External delivery does not exist in this release — an approved run finishes as Completed internally · not delivered, and nothing is sent to any external network.

Permissions

Creators can fix their own entries and schedules; deciding Pending approval entries needs a second human with an approver or admin role.

Support

If an entry will not leave Pending approval or a job stays Dead-lettered after these steps, ask your workspace admin first. LumenReach support can explain queue and approval behavior without accessing your content.