Retry Threads text posts when the container is not found - #352
Closed
paulocastellano wants to merge 1 commit into
Closed
Retry Threads text posts when the container is not found#352paulocastellano wants to merge 1 commit into
paulocastellano wants to merge 1 commit into
Conversation
Graph 24/4279009 on threads_publish is a known race for TEXT as well as media. Image, video, and carousel already recreated the container; text failed on the first hit and Nightwatch only stored the generic user message. Text now uses the same retry, and the exception message carries container_id plus Graph error_user_msg without changing the email copy. Co-authored-by: Paulo Castellano <hello@paulocastellano.com>
paulocastellano
marked this pull request as ready for review
September 11, 2026 18:35
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Nightwatch caught
ThreadsMediaContainerNotFoundExceptiononPublishToSocialPlatform(social-threads, 1.8s). The stack ispublishTextPost→publishContainer— a text-only post, no media.Graph
24/4279009(“Media Not Found” / “The media with id … cannot be found”) is a known Threads race onthreads_publish. Meta’s community reports it for text as well as images. Image, video, and carousel already recreate the container up to 3 times. Text did not, so the first miss became a hard fail and a generic Nightwatch message (Logs: Not captured).What changed
publishWithRetrypath as media.container_id,code=24,error_subcode=4279009, and Grapherror_user_msg.userMessage(and therefore the email) staysThreads could not find the processed media. Please try again.Unchanged
Log::warning; the job stillreport()s only the terminalSocialPublishException.