Skip to main content
K
Katy26722661mhfg
Participant
October 21, 2022
Answered

Content scheduler not posting to Twitter

  • October 21, 2022
  • 4 replies
  • 2053 views

I am using Adobe Express to post content to Twitter via the content scheduler. Some posts are getting through but others (half) are failing to publish, and I'm seeing the error message "As this technical issue is less common, our team will need to look into this to identify what went wrong."

 

Does anyone have a workaround? It's working fine for Instagram and Facebook. I also have a second Express account for a different organization and am able to post to Twitter from there without issue. It's just this one connection that seems to be failing. 

This topic has been closed for replies.
Correct answer Amitej S

Hi @Katy26722661mhfg

This could have occurred if there is any issue with the project you're trying to publish on Twitter. You can refer to: https://helpx.adobe.com/in/express/using/social-media-character-limits-in-scheduler.html.

 

You can also try refreshing the Access token of the social media channel connections or disconnecting the Twitter account > clearing cache/cookies of the browser > logout of your account entirely from the browser or twitter.com > Reconnecting your Twitter account on Adobe Express Scheduler.

 

Do share your observations.

~Amitej

 

 

4 replies

S
Stephen31806831e1iz
Participant
August 23, 2023

It's frustrating when technical glitches disrupt the smooth flow of content scheduling. Since you're experiencing the issue with Adobe Express on Twitter but not on Instagram or Facebook, it could be a platform-specific hiccup. Since your other Express account works well, the problem seems to be isolated to this connection.

    A
    abbas31441951uwjg
    Participant
    August 2, 2023

    Hi. This may be because the content you are uploading is sensitive. Twitter has a feature that allows you to control sensitive content. You may find help here how to turn on/off sensitive content.

    M
    micah.brickner
    Participant
    November 29, 2022

    My company is having the same issue. It seems like the failed posts are always scheduled for 8 AM ET. Is it possible that it has anything to do with a peak usage time and an east-coast datacenter for Twitter?

      Amitej S
      Community Manager
      Amitej SCommunity Manager
      Community Manager
      November 30, 2022

      Hi @micah.brickner, Could you try duplicating the project and try publishing the new one? Also, if the same project is scheduled at a different time, does it work?

      M
      micah.brickner
      Participant
      November 30, 2022

      It is different projects all scheduled for the same time on different days.
      When it's rescheduled, it works.

      --
      Micah Brickner
      Communications Director
      Eastern Mennonite Missions


      << personal info removed for privacy by moderator >>

       

      Likes

       
      Amitej S
      Community Manager
      Amitej SCommunity ManagerCorrect answer
      Community Manager
      October 21, 2022

      Hi @Katy26722661mhfg

      This could have occurred if there is any issue with the project you're trying to publish on Twitter. You can refer to: https://helpx.adobe.com/in/express/using/social-media-character-limits-in-scheduler.html.

       

      You can also try refreshing the Access token of the social media channel connections or disconnecting the Twitter account > clearing cache/cookies of the browser > logout of your account entirely from the browser or twitter.com > Reconnecting your Twitter account on Adobe Express Scheduler.

       

      Do share your observations.

      ~Amitej

       

       

      K
      Katy26722661mhfgAuthor
      Participant
      October 28, 2022

      Thanks! Yes, I think it is a character limit problem. When I'm posting in Twitter directly, Twitter truncates the URL as you approach the character limit, but I don't think the content scheduler is able to do that (as far as I can tell). It would be great if the error message could be tailored to explain this problem when it's happening - it was an easy fix once I knew what was up.

      Amitej S
      Community Manager
      Amitej SCommunity Manager
      Community Manager
      November 17, 2022

      Hey @Katy26722661mhfg, that's a fantastic suggestion. I'll definitely let our team know about this. Thanks for posting it here & feel free to drop in such ideas as they come to you 🙂

      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices