TryGhostOSS
    Ghost
    Fixed scheduler retrying publish jobs when there is nothing to publish The schedules publish endpoint returned a 404 when a job fired ahead of the scheduled time (because the post had been rescheduled to a later time) or when the post or page had since been deleted. External schedulers treat any non-2xx response as a failure and retry it, so these benign no-ops caused retry storms and noisy error logs that drown out real failures. Both cases now return a 2xx no-op so the job is treated as done. Firing well after the scheduled time without a force flag still errors, since that is a genuinely dropped publish worth surfacing. The deleted case needs a custom permissions handler, because the permission stage loads the resource and 404s a missing one before the controller runs. It swallows only NotFoundError, so permission enforcement on resources that still exist is unchanged.
    nx run-many -t lint -p ghost,ghost-monorepo
Succeeded
CI Pipeline Execution
Linux
4 CPU cores
read-write access token used
1f90be7929306
94%

Cache hits

15 of 16 tasks used cache.

Get faster results

Learn how to enable distribution.

Atomizer enabled

16 groups of tasks optimized.

© 2026 - Nx Cloud

Terms of ServicePrivacy PolicyChangelogStatusDocsContact Nx CloudPricingCompany@NxDevTools