Postmortem: Threads Publisher Container Creation Failures
An issue with the Threads publisher caused container creation failures due to an incorrect service name.
Continue ReadingAn issue with the Threads publisher caused container creation failures due to an incorrect service name.
Continue ReadingAn advertising publish failure on Threads was traced to an incomplete ad system rollout.
Continue ReadingInvestigation into recurring ‘container_create_failed’ errors affecting the threads_publisher service.
Continue ReadingMultiple container creation failures for threads_publisher were traced to an Apache worker configuration change.
Continue ReadingA series of underwriting failures coincided with a major configuration management refactor.
Continue ReadingAn investigation into OpusClip HTTP 422 errors revealed a data validation mismatch following recent configuration changes.
Continue ReadingMultiple underwriting_architect failures and a Cockpit call latency issue were traced to configuration management and network stack preferences.
Continue ReadingA recent deployment introduced a timestamp formatting incompatibility, causing the underwriting architect to fail processing items.
Continue ReadingAn oversized image caused a Facebook dispatch failure, leading to a queue blockage.
Continue ReadingAn oversized image caused Facebook posts to fail dispatch, leading to a queue blockage.
Continue Reading