Explaining the causes and fixes when X shows [Something went wrong, but don't fret — let's give it another shot.] and you cannot post

When you try to publish a post on the web client (desktop client) of X (Twitter), a red banner may appear at the top of the posting screen saying [Something went wrong, but don't fret — let's give it another shot.], preventing you from publishing the post.

In this article, I will clearly explain the causes of this error and how to deal with it.

What [Something went wrong, but don't fret — let's give it another shot.] means

The main reasons why the error message [Something went wrong, but don't fret — let's give it another shot.] appears include the following:

• A temporary glitch or system outage on X
• A browser-side problem
• A dangerous link is included
• The account is restricted
• You’ve reached the daily posting limit

I will explain each case in detail.

A temporary glitch or system outage on X

The error [Something went wrong, but don't fret — let's give it another shot.] is often caused by a temporary glitch or system outage on X.

In particular, if the timeline or posts cannot be loaded or refreshed, there is a high possibility that X is experiencing an outage, and in such cases, sending a post may fail.

If sending a post is failing because of a temporary glitch or system outage on X, save the content of your post in Notepad or drafts and then try posting again after some time.

There is nothing users can do on their side while an outage is occurring, so even if you try sending it repeatedly, it is unlikely to improve.

A browser-side problem

Some kind of browser-side problem may be temporarily preventing you from publishing posts.

In such cases, closing the browser tab or restarting the browser and then posting again may allow you to publish without any problem.

If the error [Something went wrong, but don't fret — let's give it another shot.] continues to appear even after closing the browser tab or restarting the browser, the cause may be the cache, cookies, extensions, or a VPN.

Try deleting the cache and cookies, or disabling extensions.

Also, if you are using a VPN, your post submission may be blocked because it is regarded as spam.

A dangerous link is included

Under X's policies, posting malicious links or harmful or deceptive links is prohibited, and publishing posts that contain certain links that X determines to be unsafe may be blocked.

If the post you are trying to publish contains a link, and [Something went wrong, but don't fret — let's give it another shot.] is displayed even when you close the tab and try to post again, try posting without the link.

If X has determined that destination to be dangerous, you will not be able to publish the post unless you change it to a different destination or remove the link.

The account is restricted

In rare cases, you may be unable to post because your account has been locked or temporarily restricted.

According to X's official help page, an account may be locked or its features may be temporarily restricted when suspicious automation is detected or when there is suspected rule-breaking.

If your account is restricted, a confirmation message will be displayed on X's home screen, in settings, or by email.

The account restriction will be lifted by verifying your phone number or email, or by confirming through reCAPTCHA that you are not a bot.

You’ve reached the daily posting limit

X has recently lowered the daily posting limits for some accounts to 50 original posts and 200 replies.

When you hit the posting limit, you may also see the error message, “Something went wrong, but don't fret — let's give it another shot.”

This article explains the cause in more detail and how to fix it.

Why can’t I post on X? Causes and fixes for “This request looks like it might be automated”

When trying to publish a post on X, some users are increasingly reporting that they see messages such as [Something went wrong, but don't fret — let's give it another shot.] [ This request looks like it might be automated. To protect our users from spam and other malicious activity, we can't complete this action right now. Please try again later.] and are unable to post. In this article, I’ll explain why these errors appear and what you can do when you can’t publish a post.

May 18, 2026

Conclusion

I explained the causes and fixes for cases where, when you try to publish a post on the web version of X, a red banner appears at the top of the posting screen saying [Something went wrong, but don't fret — let's give it another shot.], preventing you from publishing the post.

When the error is displayed, please use this article as a reference.