Schedule content with human approval where it matters

Draft, schedule, and route work through second-human approval, then follow each run through the durable internal queue — nothing is ever delivered to an external network.

Purpose

Plan and schedule work, route every schedule request through a second human, and follow each approved run through the durable internal queue and audit trail. External publishing does not exist in this release, so approved runs finish only internally.

Who this is for

Owners, admins, and creators who plan and schedule work and follow it through internal approval.

Prerequisites

A project with at least one draft you can schedule.
Agreement on who acts as the second human for approvals.
Reviewers with an approver or admin role.

Steps

Open the calendar and request a schedule for a draft, choosing its time and timezone.
Confirm the new entry shows Pending approval — requesting a schedule only records a pending-approval entry.
Have a second human review the entry in the Approval Queue and record a decision.
Confirm an approved entry shows Approved · scheduled on the calendar.
Watch the run move through the durable internal queue: Queued internally, then Completed internally · not delivered, or Failed if retries run out.
Review the audit trail to see who requested, who approved, and how the run finished.

Expected result

Each schedule request is recorded as Pending approval, a second human approves it, and the approved run finishes as Completed internally · not delivered — nothing is delivered to any external network.

Verification

A new schedule request shows the Pending approval label.
After the second human approves, the entry shows Approved · scheduled.
A finished run shows Completed internally · not delivered, and the audit trail names the approver.

If something goes wrong

An entry stays Pending approval: A second human must decide it in the Approval Queue; check that a reviewer with approver rights is assigned, and remind them there.
A run shows Failed: The internal worker retries a failed run automatically; read the customer-safe error recorded on the entry, fix the cause, and request a new schedule if needed.
A job shows Dead-lettered: The internal queue stops retrying after repeated failures and records the job as Dead-lettered; review the recorded error, then request a fresh schedule.

Permissions

Anyone with project access can request a schedule; approving needs a second human with an approver or admin role.

Support

If approvals are not routing as expected, ask your workspace admin to review approver roles. LumenReach support can explain scheduling and approval behavior without accessing your content.