Typo in Spanish Bluesky JSON halted auto-posting; schema fix restores English and Spanish publishing
A malformed Spanish Bluesky JSON file, caused by a localized type value and a stray trailing comma, made the nightly content-automation job crash and blocked all Bluesky posts after October 31, 2026. Manual edits and regeneration failed because the template reused the same invalid schema. The developer standardized the type field to the canonical 'progress' value, kept the text in Spanish, and added a matching English payload. Metadata was updated to mark both posts as published with their URIs, and a validation helper was introduced to catch schema mismatches early.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in