Troubleshooting and FAQ

Why does my account say Reconnect for DM access?

Direct messages and comment automations need Meta's messaging permissions on the connected account. Accounts connected before Meta approved those permissions on 2 October 2026 do not have them, so DMs and automations on those accounts answer reconsent_required.

Open Connections in the dashboard, press Reconnect on that account, and approve every permission on Meta's screen. Your posts, automations and history stay where they are.

• Connections in the dashboard

Why are liking comments and Threads mentions marked in review?

Liking comments on Instagram and reading Threads mentions need two permissions that Meta is still reviewing. Until that review passes, accounts that do not already hold them answer feature_in_review.

Reconnecting does not help yet, because Meta does not grant a permission that is still in review. Everything else works: posting, replies, private replies, DMs and the other automations. Threads reply automations work without mentions.

The first DM arrived, but nothing came after the person tapped the button. Why?

Another app, such as ManyChat, controls that conversation in Meta. Meta lets one app answer a conversation at a time. Uplika's first message to a commenter is a private reply, which Meta delivers either way, but the messages after a button tap are ordinary DMs, and Meta refuses them while another app holds the conversation. The automation's run log shows this reason.

Change it in the settings of the Facebook Page connected to the account. For Instagram, open the Page settings, then Page setup, then Instagram Conversation Routing. For Facebook Messenger, open the Page settings, then Conversation routing. Make Uplika the default app there, or remove the other app from this Page.

• Meta: Conversation Routing for Instagram
• Meta: Conversation Routing for Messenger

Why can I not send a DM to this person?

Meta lets a business message someone only within 24 hours of that person's last message. After that the window is closed: sending answers window_closed, and an automation stops at that step and records why.

The window opens again when the person messages the account. A comment does not open it. The one way to reach someone who has only commented is a private reply to that comment.

Why did a comment not get a DM?

The first DM to a commenter is a private reply. Meta allows one private reply per comment, and only within 7 days of the comment. A second automation on the same comment, or a comment older than 7 days, cannot get one.

The same automation also answers a given comment only once.

Can I send DMs on Threads?

No. Threads has no messaging API, so Uplika cannot send or read Threads DMs. On Threads, automations answer in public: the comment to reply automation answers under comments, and mentions of your account appear in the inbox once Meta's review of that permission passes.

• Automations in the dashboard

Why is there no follow check for Facebook?

Meta does not tell apps whether the person messaging a Page has liked or followed it. The follow check works on Instagram, where Meta reports whether someone who opened a conversation follows the account. On Facebook it is not offered.

Why is Like the comment locked for my account?

Uplika can like comments on Naver Blog and on Instagram accounts connected through Facebook (the account linked to a Facebook Page). On every other channel, and on Instagram accounts connected with Instagram login, the option is locked and the API answers like_unavailable.

Liking on Instagram is also still in Meta's app review, so reconnecting does not unlock it yet. When the review passes, connect the Instagram account through Facebook to use it.

• Connections in the dashboard

My automation does not react to comments. What should I check?

Check that the automation is turned on, not left as a draft. Check which posts it watches: one post, the next post, or every post. Check the keywords: if you set any, the comment has to match one.

Comments written by the connected account itself are ignored, so test from another account. The same automation answers a comment once. After you answer someone yourself in the inbox, automations hold back for 30 minutes in that conversation.

If the account shows Reconnect for DM access or another reconnect notice, reconnect it first. Without the messaging permissions and webhook subscription, Uplika does not hear the comments.

• Automations in the dashboard
• Connections in the dashboard

Why does my Facebook Page or Instagram account not show up when I connect?

On Meta's screen you choose which Pages Uplika may use. If you chose only some Pages and left this one out, Meta does not share it with us. Connect again and include the Page.

You also need a role on the Page that lets you create content. For Instagram through Facebook, the Instagram account has to be a professional account linked to that Page.

• Connections in the dashboard

Why can I not connect a second account of the same channel?

A workspace holds one account per channel. For a second Instagram account, create another workspace and connect it there. Each workspace is its own brand, with its own accounts, posts and automations.

• Connections in the dashboard

Why is my post still publishing?

Publishing is asynchronous. Text and images usually finish within seconds. Video takes longer while the channel processes it, and a long YouTube upload takes longer still. Naver Blog waits for Chrome with the extension.

A target that cannot finish ends as failed with a reason; it does not stay publishing forever. Agents can read get_post, or pass wait: true to publish to hold the answer until the post is out.

Why do my TikTok posts go up as Only me?

TikTok keeps posts from apps that have not passed its content posting audit visible to the creator only. Uplika's audit is under review. Until it passes, TikTok posts publish as Only me, and you can change the visibility in the TikTok app.

Why is my Naver Blog post waiting?

Naver Blog posts are written by the Uplika Chrome extension in your own browser. If Chrome with the extension is closed or the computer is asleep, the post waits and goes out when Chrome opens again. It waits up to seven days.

If Naver signed you out, a login window appears. Sign in there and the same post continues.

• Connections in the dashboard

Why did a scheduled Naver Blog post go out late?

Uplika sends scheduled posts at the set time, but a Naver Blog post is written by the extension, so Chrome with the extension has to be on and the computer awake at that time. If it is not, the post goes out the next time Chrome opens. When the extension is off an hour before a scheduled post, Uplika emails you.

Why does my agent get workspace_required?

You have more than one workspace and the call did not say which one. The error lists your workspaces. Pass workspaceId with the tool call, or the x-uplika-workspace header over REST. Uplika does not pick one for you, because a wrong guess would post to another brand's account.

My agent says Uplika is disconnected or unauthorized. What do I do?

Connect Uplika again from the agent's connector settings. It opens Uplika's sign-in and asks you to approve again. In Codex, run codex mcp login uplika.

If you removed the agent on the MCP page of the dashboard, its access ended and it needs a new connection.

• MCP in the dashboard