← Back to support
schedule.posturedraft

Understand schedule posture and why scheduling is unavailable

Problem

QuillDock shows scheduling as locked, paused, manual-only, blocked, or unavailable, and you need to know what that means before the next trusted run.

Who this is for

Operators reviewing schedule state on Home, Schedule, Run Detail, Backups, or Plan & Access.

What schedule posture means

  • Manual only means QuillDock still requires a successful manual publish before automation can run.
  • Paused means schedule intent may be saved, but QuillDock is waiting for a clear next step before it can queue future runs.
  • Blocked means QuillDock sees a condition that must be fixed first, such as source, target, entitlement, or write-readiness drift.
  • Active means a saved schedule is eligible to queue future runs when the next due window arrives.

Common reasons scheduling is unavailable

  • the current configuration has not completed a successful manual publish yet
  • source, target, or mapping changed after schedule readiness was earned
  • a restore completed and cleared schedule readiness
  • a scheduled run failed or completed with errors and QuillDock auto-paused future execution
  • the site is in read-only mode because of entitlement state
  • scheduling is not enabled for the site yet

Important behavior

  • QuillDock only allows scheduling after a successful manual publish on the current configuration.
  • Saved schedule intent and current effective posture are related, but they are not the same thing.
  • QuillDock can keep your saved cadence and timezone even while current execution stays paused or blocked.

What to do next

  1. Open Schedule.
  2. Read the current posture and the next requirement shown there.
  3. Fix the blocking issue or rerun the missing manual publish step.
  4. Save schedule intent again in enabled mode only after the route says the site is ready.

When to contact support

Contact support if Schedule, Home, and Run Detail disagree about the current posture, or if QuillDock keeps reporting the same pause or block reason after you complete the next required step.

Related features and docs

  • Schedule
  • Save or pause future schedule intent
  • Restore from a backup
  • Read-only mode and inactive entitlement