Reference

Troubleshooting and FAQ

Why something did not work and what to do about it: DMs and automations, connecting, publishing, Naver Blog and agents.

Each answer below is also what your agent reads. The get_help tool returns the same text by error code or by a short question, and errors that have an answer here carry its address in error.help.

Look for the error code you got, or the thing that did not happen, in the sections below.

How do I know if uplika is down?

The service status page shows whether our servers are answering right now. Check it first when sign-in, publishing or the extension stop working all at once.

DMs and automations

Why does my account say Reconnect to publish, Reconnect for DM access or Reconnect for new permissions?

An Instagram or Facebook account connected without the permission to publish shows Reconnect to publish. Posts to that account cannot go out: publishing answers reconsent_required (HTTP 422) with that account's id and the missing permission, and a scheduled post for it closes as permission_denied without being sent to Meta. Reconnect the account and allow every permission on Meta's screen. If DM access was missing too, the same reconnect brings it back.

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.

Liking comments and posts on Instagram (accounts connected through Facebook) and Threads mentions need one permission each, which Meta approved in October 2026. An account connected without that permission shows Reconnect for new permissions, and only that feature answers reconsent_required; DMs and the other automations keep working.

Open Connections in the dashboard, press Reconnect on that account, and approve every permission on Meta's screen. When connecting through Facebook, choose Edit settings and turn the new permissions on, because Continue with previous settings does not add them. Your posts, automations and history stay where they are.

An Instagram account connected through Facebook also needs two Page permissions (pages_messaging and pages_manage_metadata), because its events arrive through the Facebook Page. Some accounts connected earlier were never asked for them. If yours shows Reconnect for DM access, press it: Reconnect on an account connected through Facebook goes through Facebook again. On Meta's screen choose Edit settings and turn the new permissions on. Instagram login asks for a different set of permissions, and these Page permissions are not part of it.

If you disconnected the account instead of pressing Reconnect, its automations, contacts and conversations are kept for 30 days. Connect the same account to the same workspace within 30 days and they come back as they were, with live automations still on.

What does feature_in_review mean?

A feature needs a platform permission that is still in that platform's app review, and this account does not hold it. Reconnecting does not help until the review passes, because a platform does not grant a permission it is still reviewing. Everything else on the account keeps working.

Right now no feature is in review. Liking on Instagram and Threads mentions passed Meta's review in October 2026; an account connected without those permissions answers reconsent_required instead, and reconnecting it adds them.

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.

The same applies when you send from the inbox or when an agent calls send_dm. Meta refuses the message, Uplika answers 403 thread_owned_elsewhere, and nothing is sent. The conversation stays open; only the app that answers it is different.

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.

The person got my DM without the buttons (or nothing at all). Why?

Instagram puts a DM to someone who does not follow the account in their message requests, and a message request can only carry text. Buttons, cards and files count as attachments, so Instagram refuses them (error 1545133, "Cannot send media to this user without following them"; the code is not in Meta's public error table). Uplika then sends the text alone and records it in the run log; if even the text is refused, the run stops with this reason.

There is no setting on Uplika's side. The person can follow the account, or reply to the message, and the next messages go through. The run log shows which message went out.

Instagram refused the private reply to a comment (error 2534025). What happened?

Error 2534025, "The comment is invalid for a private reply", is Instagram's answer when it will not deliver a private reply to that comment. Instagram does not say why. Nothing was sent, and Uplika skips the public reply so the post does not claim a DM went out.

In Uplika's records it has come in two shapes. In one, every private reply from one account was refused, once for about an hour and once for about 14 hours, and then it cleared on its own; at the same moment Instagram started answering that account's DMs with a temporary block. The other shape is that certain commenters are refused every time while others on the same post get the DM; in that shape, followers have never been refused in our records. Instagram's own limits also apply: a deleted comment, a comment older than 7 days, or a comment another app already answered (that one comes back as a different error). Within 7 days of the comment, send_to_past_comments with retryRefused sends it again.

Instagram temporarily blocked my account's messages (error 368). What does Uplika do?

Error 368 with subcode 1404169 means Instagram has temporarily blocked direct messages from the account. During the same block, private replies to comments are refused with error 2534025. Instagram does not say how long it lasts. In Uplika's records it lasted about an hour once and about 14 hours once, and both times it cleared on its own.

Uplika does not drop those messages. When one DM comes back with error 368, or 16 private replies in a row are refused, Uplika holds the account's private replies: their runs wait (status waiting, with private_reply_held in the run log) instead of failing, and Uplika stops calling Instagram for them. After 15 minutes it tries one held message, then again every 30 minutes. When two in a row go out, it sends the held messages newest first, a few a minute, one per person per automation, and posts the public reply under the comment after the DM.

A private reply is only allowed within 7 days of the comment, so a message still held then ends with a reason saying the block did not lift in time. A DM after a button tap waits until that person's 24-hour window closes. Nothing needs to be done in Uplika.

Instagram refused a DM because message access is turned off (error 200). What does it mean?

Error 200 here means the owner of the Instagram account turned off message access for connected tools in the Instagram app. While it is off, Instagram refuses the messages Uplika sends for that account, private replies to comments included, so nothing goes out. Sending from the inbox or with send_dm answers dm_access_disabled, and an automation ends that run with this reason. Sending again gives the same answer until access is turned back on.

Turn it on in the Instagram app: Instagram Settings > Messages and story replies > Message controls > Connected Tools > Allow Access to Messages. If it is already on, reconnect the account in Uplika. In Uplika's records one account could send again without reconnecting, and another right after reconnecting.

Comments refused while access was off can still get the automation within 7 days of the comment. After turning access back on, ask your agent to send the automation to past comments again, including the refused ones (retryRefused).

Error 508 (Link can't be shared) means Instagram is not letting this account share links in messages right now, and Meta's message points to the account's status. While it lasts, Instagram refuses the messages from that account that have a link in their text, so nothing was sent. Sending from the inbox or with send_dm answers dm_link_sharing_restricted, and sending the same message again gets the same answer.

Check the account's status in the Instagram app, and keep links out of the message text until it clears. In one case in Uplika's records, a message with the link only in a URL button went out while the messages with the link in their text were refused.

An automation ends that run with this reason. PNG and JPEG photos and videos in an automation's file blocks go as attachments, not as a link in the text. If Instagram refuses such an attachment with this error, Uplika does not send it again as a link, because a link in the text gets the same refusal.

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. Instagram itself can report the window closed even while Uplika's badge still shows it open; Uplika then closes its own record too, and the person has to message again.

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.

If another app connected to the account already sent the private reply, Instagram refuses ours with error 2534023. Uplika counts that comment as already answered, not as a failure, and the run shows as Replaced (superseded).

If the comment was deleted before the DM went out, there is nothing left to reply to. Instagram refuses with error 2534014 on accounts connected with Instagram login, or error 1893060 on accounts connected through Facebook, and nothing is sent. People often delete a comment and post it again. The new comment is a separate comment and is answered on its own.

Can an automation answer comments that were posted before it was turned on?

Yes, for comments from the last 7 days. An automation normally reacts only to new comments, but it can also be sent to the comments already on the post. Ask your agent to send the automation to past comments, or call the past-comments endpoints of the API. It first shows how many comments would get it and how many would not, and sends only after you confirm. The automation has to be turned on first.

It cannot reach everyone. Meta allows one private reply per comment and only within 7 days of the comment, so older comments are left out, and a comment that another tool already answered by DM is refused by Meta. Comments that already have a reply from your account are skipped unless you ask to include them, and a person who commented several times gets it once, on their newest comment.

Sending is paced. Meta allows 750 private replies per hour per account and your live automations use the same allowance, so a post with many comments takes hours. Every comment that was answered appears in the automation's run history.

Do comments on an ad reach my comment automation?

Yes, when the ad promotes a post you had already published. Instagram sends those comments as comments on the ad, and Uplika maps each one back to the original post, so automations set to that specific post, to the next post and to any post all react to it. The run history carries an ad_comment line with the ad id.

An ad created on its own, without a published post behind it, has no original post. Comments on it reach only automations set to any post.

The private reply rules are the same: Meta allows one private reply per comment and only within 7 days of the comment. Sending an automation to past comments does not reach ad comments, because Instagram does not list them among the post's comments; Uplika has seen this on its own records. Ad comments are handled as they arrive.

My Instagram account has an age restriction (minimum age) and the comment automation sends no DM. Why?

Meta does not give apps the comments on age-restricted media. While a minimum age is set on the account or on a post, the comments there may not reach Uplika, and an automation that never sees the comment does not start, so no DM goes out and the run history stays empty. There is no setting to change on Uplika's side.

Remove the minimum age in the Instagram app: open your profile, tap the menu in the upper right, choose Business tools and controls (Creator tools and controls on a creator account), tap Minimum age, and remove the default age and every country age. A branded content post can carry its own minimum age, so check that post too. Then leave a test comment from another account and see whether the DM arrives.

Comments posted while the restriction was on do not come back later on their own. Meta allows one private reply per comment and only within 7 days of the comment, so after removing the restriction you can ask your agent to send the automation to past comments for the ones that are still inside that window.

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. An account connected before Meta approved the mentions permission in October 2026 needs one reconnect for mentions.

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.

To use it on Instagram, connect the account through Facebook. An account connected through Facebook before Meta approved the like permission in October 2026 needs one reconnect: press Reconnect on Connections, choose Edit settings on Meta's screen and turn the new permission on.

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.

Instagram sometimes skips comment notifications for a single post. For automations that watch a specific post or the next post, Uplika also checks that post's comments every 5 minutes for the first 6 hours after it goes up, then every hour until 30 days, and every 5 minutes for 7 days once it finds a missed one. A comment found this way gets the same DM and public reply, up to about an hour late, and its run log starts with gap_comment.

Connecting accounts

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.

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.

On Facebook, and on Instagram connected with Facebook login, Meta's screen is where you choose which Pages Uplika may use. When you connect another workspace, keep the Pages already connected elsewhere ticked in that list. A Page left unticked loses its connection in every workspace.

If this came back while you were reconnecting a connection that had ended, the channel signed you in as a different account than the one connected here. Do not disconnect. Log in to the channel as the original account (switch accounts there), then press Reconnect again. Reconnect deletes nothing. Disconnecting deletes that account's scheduled posts and keeps its automations and conversations for 30 days.

YouTube says the Google account has no channel (youtube_channel_required). What do I do?

YouTube answered that the Google account behind this connection has no YouTube channel that can take uploads. You see it in two places: connecting YouTube stops with this message, or a YouTube post fails with youtube_channel_required. Reconnecting with the same Google account gives the same result.

Reconnect and, in Google's account list, pick the account that owns the channel. If the channel belongs to a Brand Account, pick the channel itself there, not your personal account. If the account has no channel yet, finish creating one on YouTube with that account, then connect again and send the post again. A failed post keeps its video for 7 days.

For agents: errorCode youtube_channel_required is not retryable. Calling retry_post before the channel is fixed gives the same result; after the person reconnects the right channel, retry_post sends the same video.

I disconnected an account. Why can I not edit or delete its posts by post id?

Disconnecting an account keeps the record of posts that already went out or failed. They stay in Sent with a Disconnected badge, and the posts themselves are still on the channel. Uplika no longer holds a login for that account, so editing, deleting, retrying, replying or reading metrics by post id answers account_disconnected.

Reconnect the same account on Connections. The records join the connection again and the same post ids work again. If you connect a different account instead, the old records stay Disconnected.

Disconnecting also keeps that account's automations, contacts and conversations for 30 days. They are hidden while the account is disconnected. Reconnect the same account to the same workspace within 30 days and they come back as they were, with live automations still on. After 30 days they are deleted.

Why does a channel answer account_expired, and why does refreshing the account not fix it?

account_expired means the channel no longer accepts the sign-in behind this connection. The sign-in expired or was revoked on the channel's side, and the channel does not tell us which.

On Facebook, and on Instagram connected with Facebook login, the connection also ends when Facebook removes Uplika's access to the Page. That usually happens when the same Facebook account connects to Uplika again, for another Page, an Instagram account, another workspace or another Uplika account, and leaves the Page unticked in the list of Pages on Meta's screen. Reconnect it, and keep every Page you use with Uplika ticked in that list.

Refreshing an account (refresh_account, or POST /v1/accounts/{id}/refresh) only re-reads its name and profile picture, and the categories on Naver Blog. It does not renew a sign-in. Reconnect the same account on Connections. The same connection carries on, so its post history and automations stay.

While a connection is expired, its automations do not react to new comments or messages. On Instagram and Facebook, comments posted in the meantime can still get the automation within 7 days of the comment: after reconnecting, send the automation to past comments.

Why can't I connect my Ghost(Pro) Starter site?

Uplika connects to Ghost with the Admin API key of a custom integration. Ghost(Pro)'s Starter plan does not include custom integrations or the Admin API, so Ghost refuses that key and the connection answers ghost_plan_limit.

Publisher and the plans above it include custom integrations, and so does a self-hosted Ghost. After you change plan, create the custom integration and connect again with its API URL and Admin API key.

Where do I find the API URL and Admin API key for Ghost?

In Ghost Admin, open Settings, then Integrations, and choose Add custom integration. Every custom integration comes with a Content API key and an Admin API key. Copy the API URL and the Admin API key shown there into Uplika's connection form; the Content API key does not work for publishing.

On Ghost(Pro) the API URL ends in .ghost.io even when your site uses its own domain, so paste the API URL from the integration, not your public site address. If you regenerate the Admin API key or delete the integration, the connection stops working; connect again with the new key.

Where do I create the application password for WordPress?

In WordPress, open Users, then Profile (people who are not admins only see Profile in the menu). In the Application Passwords section, enter a name you will recognize and choose Add Application Password. WordPress shows the password only once, so copy it right away and paste it into Uplika's connection form with your site address and WordPress username.

Your WordPress login password does not work here, and WordPress only offers application passwords on sites served over https. If the section is missing, a security plugin may have turned it off. The user needs the Author role or higher to publish posts and upload photos. If you delete the application password in WordPress, the connection stops working; create a new one and connect again.

Why does WordPress refuse details I know are right?

WordPress gives the same answer for a wrong password, a user that does not exist and a request whose Authorization header never reached it, so the connection cannot always tell them apart. Check the username and password first: the username is your WordPress login name or email address, and the password is an application password, not your login password.

If both are right, your host or a proxy in front of the site may be removing the Authorization header. Ask your host to pass that header through to WordPress, then connect again. If the message says the request was blocked before WordPress could answer, a security plugin or firewall stopped it: allow REST API requests from Uplika in its settings, then connect again.

Can I connect a WordPress.com site?

Yes. On the Connections page, pick WordPress, choose WordPress.com, approve Uplika on WordPress.com and pick the one site Uplika should post to. Uplika gets access to that site only. A WordPress.com site has no application passwords, so typing a wordpress.com address in the self-hosted form answers wordpress_com_site.

If your WordPress runs on your own hosting, choose My own WordPress install instead and connect with its https address and an application password.

How can a client connect their own channel without sharing a password?

Send them a connection link. On the Connections page press Send a connection link to a client, pick the workspace and the channels, and copy the link, or ask your agent to call create_connect_invite. The link page offers only the channels that show up when you make the link; channels a link cannot connect are greyed out.

Your client opens the link on their own device. Most channels have them sign in on the channel's own screen and approve; channels that connect a page or a board then ask them to pick one. Channels that connect with an app password or a bot token ask for it on the link page itself; Uplika keeps it encrypted, and even the person who made the link cannot see it again. They do not sign up for Uplika and nobody sees their password. The account then shows up in that workspace like one you connected yourself.

A link works for 72 hours and connects each of its channels once. If it expired, was cancelled or was already used for that channel, make a new one. You can cancel a link from the list on the Connections page; accounts already connected through it stay until you disconnect them.

Why does it say audio cannot be added to my Instagram reels?

Meta offers audio on reels only to Instagram accounts connected through Facebook. An Instagram account connected with Instagram login cannot take audio, and reconnecting the same way does not change that.

On the Connections page, open the account's menu and choose Reconnect through Facebook, then publish again. The account's scheduled posts and automations stay. You can also publish the reel without audio.

My Discord connection stopped working

Uplika posts to Discord through the webhook URL you pasted. If someone deletes that webhook in Discord, resets its URL, or deletes the channel it belongs to, the old URL stops working and the connection shows as expired.

In Discord, open Server Settings, then Integrations, then Webhooks. Click New Webhook for the channel (or open the one that is there) and press Copy Webhook URL, then reconnect Discord in Uplika with the new URL.

Pinterest says there is no board

Every Pin goes on a board. When you connect Pinterest, Uplika reads your boards and asks you to pick a default one. An account with no board cannot be connected, and Uplika sends you back to create one first.

A post that names no board goes to the default board. If the connection has no default board, for example because the board was deleted and the list was refreshed, the post is refused. Pick a default board under Connections, or choose a board on the post.

My personal Pinterest account does not connect

Pinterest does not let Uplika read the boards of a personal account, so the connection stops before you can pick a board. A business account connects, and switching to one is free. We checked this on November 4, 2026: a personal account was refused, and the same account connected after it was switched to a free business account. We asked Pinterest to allow personal accounts, and on November 7, 2026 Pinterest replied that it cannot approve this at this time.

In your Pinterest settings, switch the account to a free business account and answer the short questions Pinterest asks about your business. Then connect Pinterest again under Connections.

Instagram says my account was switched to a personal account (error 10)

The Instagram account was switched from a professional account to a personal account. Instagram only lets connected tools like Uplika work with professional accounts, so while the account is personal, publishing, reading its posts and refreshing the connection all answer instagram_personal_account.

If the account is already connected, switch it back to a professional account (business or creator) in the Instagram app. The connection stays as it is, so there is no need to reconnect. After switching back, send the same post again.

If you saw this while connecting, switch the account to a professional account (business or creator) in the Instagram app first, then connect Instagram again under Connections.

My agent says Google Analytics, Google Ads or Meta Ads is not connected

These connect per workspace, not per person. integration_not_connected means the workspace in this request has no connection for that service. Connect it under Connections in the dashboard, with that workspace selected.

integration_reconnect_required means Google or Meta ended the connection, for example because Uplika's access was removed from the Google account or the Meta login. Connect the same account again under Connections. The daily budget cap of a Google Ads or Meta ad account stays when you reconnect the same ad account.

How do I connect a Google Ads account so my agent can use it?

A workspace connects one Google Ads account. Under Connections in the dashboard, connect Google Ads, sign in with a Google account that can manage it, and pick the account. Accounts under a manager account are listed one level down. The manager account itself is not listed, because it cannot hold campaigns. google_ads_no_accounts means this Google account can manage no account that holds campaigns.

Your agent then reads with get_ad_account, get_ad_insights, list_ads and get_ad, and writes with create_ad_campaign, set_ad_status and update_ad_budget. It changes what already exists with update_ad_campaign, update_ad_group, update_ad and update_asset_group, adds to it with create_ad_group, create_ad, add_ad_keywords and create_asset_group, and removes with delete_ad. find_ad_targeting finds audiences, topics and languages by name, set_ad_targeting sets who and where an ad group reaches, create_custom_audience makes a custom audience from words and sites,, set_ad_extensions sets a campaign's sitelinks, callouts, structured snippets and call number, set_ad_bidding changes a campaign's bid strategy and target, and create_conversion_action makes a website conversion action and returns its tag. create_demand_gen_campaign, create_display_campaign and create_performance_max_campaign create the other campaign types, and fit_ad_images makes image copies in the shape their image fields need. New campaigns are always created paused. Agents that connected before need to approve the ads permission once to write. google_ads_not_configured means Google Ads connection is not open on Uplika's side yet.

Connecting Google Ads did not finish

If you cancelled on Google's screen, nothing was connected. If the connection link expired or Google did not finish the sign-in, start again under Connections.

google_ads_scope_missing means the Google Ads permission was left unchecked on Google's screen: start again and allow it. google_ads_no_refresh_token means Google did not give long-lived access: remove Uplika from your Google account's third-party access, then connect again.

google_ads_session_mismatch means this browser is not signed in to the Uplika account that started the connection: sign in and start again. Do not use a connection link someone else sent you.

Google Ads asks for 2-Step Verification

Google Ads does not let a Google account manage an ad account through an app until that Google account has 2-Step Verification turned on. Uplika cannot turn this on for you.

Turn it on in that Google account, then connect again under Connections, or repeat the request if the account is already connected.

How do I connect a Meta ad account so my agent can use it?

A workspace connects one Meta ad account, and it can keep a Google Ads account connected at the same time. Under Connections in the dashboard, connect Meta Ads, sign in to Meta, choose the business portfolio and the ad account, and allow Uplika to read ads. This connection reads: your agent can see the account, its campaigns and their numbers.

To let your agent turn ads on or off, change budgets, boost posts as paused ads, and create, change or delete campaigns, ad sets and ads, press Allow management on the Meta Ads card and confirm in Meta. Until then those requests answer ads_write_not_granted and change nothing. Then set a daily budget cap on the card, or choose No limit there: until one of them is chosen, turning ads on and raising budgets are refused.

meta_ads_no_business means this Meta login has no business portfolio Uplika can read: create one in Meta first, then connect again. meta_ads_no_accounts means that business has no ad account this login can read. meta_ads_not_configured means Meta Ads connection is not open on Uplika's side yet.

Connecting Meta Ads did not finish

If you cancelled on Meta's screen, nothing was connected. If the connection link expired or Meta did not finish the connection, start again under Connections.

meta_ads_scope_missing means Meta returned the connection without the ads permissions Uplika asked for: ads_read, and after pressing Allow management, the ads management permission. Start again and, on Meta's screen, pick the business portfolio that owns the ad account and keep the permissions on. Without ads_read Uplika cannot read anything in the ad account, and without the management permission it cannot change anything.

meta_ads_session_mismatch means this browser is not signed in to the Uplika account that started the connection: sign in and start again. Do not use a connection link someone else sent you.

How do I connect Google Analytics so my agent can read it?

A workspace connects one GA4 property. Under Connections in the dashboard, connect Google Analytics, sign in with a Google account that can view the property, and pick the property. Another workspace can connect a different one.

Your agent then reads it with get_analytics_report, get_analytics_realtime and get_analytics_metadata in that workspace. Uplika only reads: nothing in Google Analytics changes. If connecting says Google Analytics is not available yet, it has not been opened for your account yet.

Connecting Google Analytics did not finish

If you cancelled on Google's screen, nothing was connected. If the connection link expired or Google did not finish the sign-in, start again under Connections. Uplika needs permission to view your Analytics data, so leave that box checked on Google's screen.

google_analytics_session_mismatch means this browser is not signed in to the Uplika account that started the connection: sign in and start again. Do not use a connection link someone else sent you.

A connection that did not finish changes nothing: a property you already connected stays connected.

Google ended my Google Analytics connection

Uplika reads your property with a lasting permission from Google. When Google ends it, for example because access was removed from the Google Account, reads answer integration_reconnect_required. Connect the property again under Connections.

If connecting says Google did not give lasting access, remove Uplika's access from your Google Account first, then connect again. Google then gives a new permission.

This Google account cannot view my GA4 property

Uplika lists only the GA4 properties the Google account you signed in with can view. If yours is not there, that account has no role on it. Ask an administrator of the property to give that account the Viewer role or higher, or connect with an account that already has one.

If reads answer analytics_no_access, the connected account lost its role after you connected. Uplika keeps the connection. Once the role is back, the next read works again.

Why do I have to buy X credits before posting to X?

X charges for each API call an app makes, and X sells that usage as credits bought in advance. Uplika sells X usage the same way: you top up X credits, and each post, reply, attached file, alt text, delete or metrics read on X comes out of that balance at Uplika's price for that action.

You only spend what you put in, so there is no bill at the end of the month. The balance belongs to you, not to one workspace, so every workspace you own draws from the same X credits. Connecting an X account needs enough balance for one post.

Why does LinkedIn need to be reconnected every 60 days?

LinkedIn gives apps like Uplika a connection that lasts 60 days and cannot be extended in the background. When it ends, the only way back is to connect again. This is how LinkedIn works for every app that is not one of its partners.

A week before the end, the LinkedIn card under Connections turns amber and Uplika sends one email (turn it off under Settings, Email, Warnings). Reconnect from that card to start a new 60 days. Your posts and schedules stay as they are.

A scheduled post set for after the end date goes out as planned if you reconnect before its time. If its time comes while the connection has ended, it is marked failed; reconnect, then send it again.

Can I post to a LinkedIn company page?

Not yet. Uplika connects personal LinkedIn profiles only. Posting to a company page needs a separate approval from LinkedIn, and Uplika does not have it yet. It is listed as coming soon under Connections.

If you manage a company page, you can still post to your own profile, and share that post to the page from LinkedIn.

Publishing

WordPress could not confirm my post. Did it go out?

It may have. The site did not answer in time, often because a slow plugin runs while the post saves. Uplika then looked once for a post by the connected user with exactly the same title and body and did not find one. A plugin that changes the body on save makes the post look different from what was sent, so it can be on the site anyway. Check the site first, including drafts.

If the post is there, you are done, and this failed line can stay as it is. If it is not there, send it again. Uplika never resends on its own, and for 10 minutes the same content answers duplicate_post so a post cannot turn into two by accident. Pass force: true once you have checked, on a new post or on retry_post.

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 the browser 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.

My image was rejected as incomplete or damaged

When an upload finishes, media_complete reads the end of the image. If the end marker is missing it decodes the whole file, and if that fails the file is discarded with image_unreadable: the transfer was cut off before the last bytes arrived, so the copy on our side has no ending. Nothing was published with it.

Upload the same file again from the device: media_presign and a fresh PUT, or the upload link if a person is sending it. The copy on the device is usually fine, so a second upload normally goes through.

If a post already failed with this code on one of its targets, do not retry that post: the same bytes fail at the same place. Upload the file again and create a new post with the new media id.

If this keeps happening from the same client, the transfer on the sending side is being cut off. Hand the file over with media_upload_link so the person uploads it from their browser, or give media_from_url a public https address and let the server fetch it.

media_complete says the upload did not finish

When media_complete answers media_not_uploaded, the reason field says why. not_arrived means no bytes reached the upload address yet: the PUT has not finished, or it never ran. PUT the file to uploadUrl, wait until that PUT succeeds, then call media_complete again with the same id. empty means the file arrived with no bytes: PUT the whole file again and complete the same id. The response also says until when the address works.

upload_url_expired means the signed address ran out before the file arrived, so the same id cannot receive it any more. Start again with media_presign for a new id and uploadUrl. A client that cannot send an HTTP PUT itself can use media_upload_link so the person uploads from their device, or media_from_url when the file has a public https address.

When publishing answers media_not_uploaded, one of the media ids was never confirmed, so nothing was posted. Finish the upload, complete the id, then publish again.

Why does YouTube say Uplika's daily limit ran out (youtube_quota_exhausted or youtube_daily_cap)?

Uplika works with YouTube inside a daily allowance that Google sets for Uplika as a whole, and everyone who uses Uplika shares it. When it runs out, YouTube refuses uploads, edits, comments, metrics and even connecting a channel until it refills at midnight Pacific time. When only the number of new uploads ran out, reading, editing and connecting still work. youtube_quota_exhausted answers a request and carries resetsAt; youtube_daily_cap is the reason recorded on a post that was not sent.

It is not a problem with the Google or YouTube account, so reconnecting does not help. Wait until the time in resetsAt, then try again, or send a post that was not sent with retry_post. A scheduled post that goes only to YouTube keeps its schedule: publish_now answers 429 with resetsAt and changes nothing, so if it is due before resetsAt, move it later with update_post. Uplika's YouTube search for research uses a separate allowance, so search can still work on a day publishing is paused, and the other way round. Uplika has asked YouTube to raise the limit.

YouTube refused the video details and Uplika points at the language code (youtube_language_rejected). What do I do?

When the upload started, YouTube refused the video details with "Request contains an invalid argument." and did not say which field. The post had a language code of the title and description, and the most likely cause is that code: YouTube takes language codes it knows, such as en-US or ko, and a country code such as US is not a language. Nothing was uploaded, and the video of a post that failed this way is kept for 7 days.

In Sent in the dashboard, open the post with Write again. Change the language to a code such as en-US or ko, or clear it, then send. Sending the same post again would send the same code, so Retry is not offered.

For agents: the target's errorCode is youtube_language_rejected and retryable is false. Fix options.youtube.defaultLanguage to a language code such as en-US or ko, or leave it out, then publish again as a new post. retry_post would send the same code.

Editing a YouTube video failed with "Precondition check failed." Why?

That video has a Test & compare running in YouTube Studio (an A/B test of titles or thumbnails). While the test runs, YouTube does not let the title change, so the edit was refused and nothing on the video changed. The video stays up as it was.

Stop the test in YouTube Studio (Analytics, Reach tab, Manage test) or wait for it to finish; YouTube aims to finish a test within two weeks. Then make the edit again. Trying before then gives the same result.

For agents: the edit closes with errorCode platform_rejected_content and our sentence in the warning; the channel's reason is UPDATE_TITLE_NOT_ALLOWED_DURING_TEST_AND_COMPARE. Do not publish the video again. Call update_post again after the test is stopped or finished.

Editing a YouTube video right after it went up answered youtube_video_not_listed. Why?

Before an edit, Uplika reads the video back from YouTube. YouTube did not return it, so nothing on the video changed and it keeps the privacy it had. A video that went up in the last few minutes is sometimes not listed in that read yet. A video deleted in YouTube Studio looks the same, and the two cannot be told apart from here.

If the video went up in the last few minutes, wait a few minutes and make the same edit again. Do not upload it again. If you deleted it in YouTube Studio, delete the post in Uplika to clear the record.

For agents: the edit closes with errorCode youtube_video_not_listed, which is retryable. Wait a few minutes, then call update_post once more; do not publish the video again. If the video was deleted in YouTube Studio, call delete_post to clear the record.

Reading or replying to comments on a YouTube video answered comments_closed. Why?

That video is not taking comments right now, so there are no comments to read and a reply cannot go up. Either the channel turned comments off on that video, the video is set as made for kids (YouTube keeps comments off on those), or the video is private (a scheduled video stays private until its publish time). When YouTube refuses a comment without giving a reason, it closes with this code too, and the cause is usually one of these. The video itself is fine and the account does not need reconnecting.

If the channel turned comments off, turning them on for that video on YouTube lets replies go up. A scheduled video takes comments from its publish time, so a reply sent after that is a new reply. On a video that stays made for kids or private, sending the reply again gives the same result.

For agents: reading replies answers 400 with code comments_closed. A reply closes its target as failed with errorCode comments_closed and retryable false. Do not send the same reply again now. On a scheduled video, a new reply can go up after its publish time. Do not change the video's privacy or audience (made for kids) setting on your own; that is for the person to decide.

Why do my TikTok posts go up as Only me?

Uplika passed TikTok's content posting audit on October 9, 2026. Since then a TikTok post goes up with the visibility you choose when you publish, and your TikTok account no longer has to be private.

Posts made before that date went up as Only me, because TikTok shows posts from apps that have not passed the audit to the creator only. They stay that way until you change the visibility in the TikTok app. If a new post still shows Only me, check the visibility you picked for that post.

Why do replies and metrics on a post answer post_unavailable or post_deleted?

post_unavailable means the channel no longer returns that post to the account that published it. That is what the channel answers for a post deleted in its app, so its replies and metrics cannot be read and asking again will not change it. Our record still shows the post as published because nothing told us it was deleted. To clear the record, call delete_post on it. Threads, and Instagram connected through Facebook, treat a post that is already gone as deleted, so the call succeeds and the record is marked deleted. Instagram connected through Instagram login cannot delete through the API, so delete_post reads the post once more and, when Instagram still does not return it, clears our record without calling Instagram. YouTube answers that a deleted video cannot be found, so delete_post records it as deleted without changing anything on YouTube. Editing an imported video that was deleted answers the same code and changes nothing; editing a video Uplika uploaded answers youtube_video_not_listed instead.

post_deleted means you already deleted that post with delete_post. Its replies and metrics are no longer read and nothing is sent to the channel. On a post that went to several channels, delete_post refuses before touching any channel when one of them cannot be deleted on that account (for example Instagram connected through Instagram login), and says nothing was deleted, unless that Instagram post is already gone from Instagram: then its record is cleared without a call and the other channels are deleted as usual. If a channel fails after another was already deleted, the message names which channel was deleted and which one is unchanged, and the record marks only the deleted one.

reply_parent_unavailable means a reply did not go out because the channel no longer returns the post or comment it was for, most likely because it was deleted in the channel's app. Instagram reports it after reading that post or comment once more. Threads reports it when it refuses to create the reply because it cannot find that post or comment. Nothing was posted, and sending it again or changing the text gives the same result. Reply to a post or comment that is still there. If the post itself was deleted, delete_post on it clears our record.

Facebook says to confirm my identity before I can publish as my Page (error 368). What do I do?

Facebook answered error 368 with subcode 4854002: "Confirm your identity before you can publish as this Page. Open the Facebook app on your phone and follow the instructions." Until that check is done, Facebook refuses every post to that Page, scheduled posts included, and changing the text or the files does not help. This is not an ended sign-in, so Uplika leaves the connection as it is.

Open the Facebook app on your phone and follow its instructions. Then send the failed post again: in the dashboard, open the post and press Write again; an agent publishes the same content again. The photos and videos of a post that failed this way are kept for 7 days.

Facebook says "Unsupported post request. Object with ID ... does not exist" when I edit or comment on a post. What do I do?

Facebook answered error 100 with subcode 33: the post does not exist, cannot be loaded because of missing permissions, or does not support this action. In practice Facebook has stopped letting apps reach that post. It may have been deleted or taken down on Facebook, or it may still show on your Page while apps cannot reach it. Nothing changed on Facebook, and sending the same edit or comment again fails the same way.

Check the post on your Facebook Page. If it is still there, edit it or comment on it in Facebook itself, and do not publish it again or the same post will be on your Page twice. If it is gone, delete it in Uplika to clear the record; you can then publish it again as a new post.

Reading the post's comments or metrics can get the same answer ("Unsupported get request"). Then Uplika cannot read its comments or metrics, and asking again gives the same answer. Check the post on your Page the same way: if it is gone, delete it in Uplika to clear the record; if it is still there, read its comments and metrics in Facebook itself.

My Facebook story video was refused for its length. How long can it be?

Uplika measures a Facebook story video before sending it. A story video has to run 3 to 60 seconds, and one outside that is refused before anything is sent. Nothing from that request went out, on Facebook or on any other channel in it.

Meta's Page Stories documentation gives two numbers for video, 3 to 90 seconds and a 60-second limit, so Uplika uses the shorter one. Trim the video to under 60 seconds and send it again. If you want the longer video up as it is, a reel is another way: a Facebook reel runs 3 to 90 seconds and, unlike a story, stays on your Page as a post.

For an agent: the 422 code is facebook_story_duration. limit is the bound the video broke and actual is its length in seconds, to one decimal. Sending the same file again gets the same answer, so trim the video, upload it again and publish that. Whether to post it as a reel is the person's call: ask them before changing the post type.

Instagram says "Media upload has failed with error code 2207082" (or 2207085). What do I do?

Instagram failed while processing the uploaded file and said only "Media upload has failed with error code" with a number. Meta's error table does not list 2207082 or 2207085, and Instagram does not say why. Nothing was posted, and the photos and videos of a post that failed this way are kept for 7 days.

If the reel had audio and the video has no sound of its own (an AI-generated clip, motion graphics, or a screen recording saved without sound), the video's own sound volume (videoVolume) has to be 0. Uplika sends 0 for such videos, so retry the post once: in Sent in the dashboard, press Retry on that post's row. If it fails again with the same code, send it again as a new post with videoVolume at 0, remove the audio, or save the file again with a sound track.

If the reel had no audio, retry the post once: in Sent in the dashboard, press Retry on that post's row. If it fails again with the same code, save the file again and send it as a new post.

For agents: the target's errorCode is instagram_upload_failed and retryable is true. Call retry_post once. If the reel had options.instagram.audio and the video has no sound track of its own, Uplika sends videoVolume 0 for it, the retry included. If it fails again with the same code, publish it as a new post: with audio, set options.instagram.audio.videoVolume to 0, or drop options.instagram.audio, or export the file again with a sound track; without audio, export the file again. A 2207085 that comes at the publish step, after Instagram finished processing the media, is a different code: see instagram_publish_failed.

Instagram answered the publish with "Generic internal error" (code -1, subcode 2207085). What do I do?

Instagram answered with an internal error at the last step of posting and did not say why. Before recording the failure, Uplika looks for the post among the account's latest posts. If it is there, the post is recorded as published with a note, and you should not send it again.

If the post is recorded as failed, your files are kept for 7 days. Look at your Instagram account first. If the post is not there, retry it once: in Sent in the dashboard, press Retry on that post's row. If the same error comes back on this account, try posting it from the Instagram app.

For agents: the target's errorCode is instagram_publish_failed and retryable is true. The message says whether Uplika checked the account's latest posts. There is no automatic retry, and the files are kept for 7 days. If the message says the post is not there, call retry_post once. Otherwise have the person check the account first, then call retry_post once. If it fails the same way again on the same account, tell the person to post it from the Instagram app instead of retrying further.

With a search word, Instagram's audio search returns only royalty-free music from Meta's Sound Collection, so an artist or song name will not find that song. Popular songs appear in the trending list, which you get by searching without a word. Trending music differs per account, and some accounts only get royalty-free music.

Use an id from the same account's own results. If Instagram does not accept the audio, search again and publish with another id. Audio goes on reels only, and each volume is a whole number from 0 to 100. For a reel with narration, keep the video's own sound at 100 and set the added audio around 20. Instagram cannot preview a reel with audio before it is published.

Can I find the newest or most popular sounds, see how many reels use a sound or when it was made, or get a file for a popular song?

Instagram's audio search has no option to sort by newest or most popular and no date filter, and Instagram does not give how many reels use a sound or when it was made. The only popular list is the account's trending list, which you get by searching without a word, and it differs per account. Instagram returns only audio cleared for use outside its app, so a sound trending in the Instagram app may be missing.

A search word has to match the sound's title as written, including spaces: the same title written without a space can return nothing. If the sound you want is not in the results, add it in the Instagram app when you post there, or publish without audio.

Popular songs in the trending list come with a link that opens the sound on Instagram, and the list gives no audio file to listen to or download.

How do I post a trial reel, and how do I know whether it was shared to my followers?

A trial reel is shown only to people who don't follow you, so you can test an idea without your followers seeing it. Set options.instagram.trialReel on a reel: performance lets Instagram share it with your followers on its own if it does well, and manual keeps it a trial until you share it from the Instagram app. Leave it out for a normal reel. Trial reels are reels only, and a value other than those two is refused instead of posting a normal reel.

Instagram does not tell apps whether a reel is still a trial or has been shared to your followers, so Uplika cannot show it. Check the reel in the Instagram app. Views, likes, comments and shares are read the same way as any reel.

Instagram decides which accounts can post trial reels. Its Help Center says the account has to be public, a professional account needs at least 200 followers, and an account that isn't eligible to be recommended can't use them. Instagram's developer documentation gives no number. If Instagram refuses the account, the post fails with instagram_trial_reel_ineligible and nothing is posted. A normal reel goes to all of your followers, so your agent should ask you first, then publish the same media again as a new post without trialReel. retry_post sends the trial setting again and fails the same way.

Why did @everyone in my Discord post not notify anyone?

By default Uplika sends Discord posts with mentions turned off, so @everyone, @here, role and user mentions show as text but notify nobody. This keeps an agent from pinging a whole server by accident.

To notify people, set the Discord option Mentions when you publish: users notifies only the people mentioned, all also notifies roles, @everyone and @here.

Why can't Uplika post to my Discord forum channel?

A forum or media channel in Discord needs a new thread with a title for every post, and Uplika does not create threads. Discord refuses a webhook post there without one.

Make a webhook for a regular text channel instead and reconnect Discord with that URL. Once a forum webhook has been refused, Uplika stops sending to it and tells you before it tries again.

My Pinterest board is not in the list

Uplika lists the public boards of the connected account and the group boards it takes part in. Secret boards are not listed, because Uplika does not ask Pinterest for access to them.

Uplika reads the board list when you connect. A board you make on Pinterest afterwards shows up after you refresh the connection under Connections. If a board was deleted or made secret, Pins sent to it are refused; pick another board and send the post again.

Why is a fee added when I top up X credits?

The payment processor charges a fee on every payment, and where your country charges tax on the purchase, that is added too. Both are added to the amount you pay, so the credits you receive are the full amount of the pack you picked.

The fee is the processor's own fee for that payment. Cards issued outside the processor's country carry a higher fee, set by the processor.

What happens when my X credits run out?

Uplika checks your X credit balance before it calls X. When the balance cannot cover a post, nothing goes out to X and nothing is charged: the request answers x_credits_insufficient with a link to top up. Deleting a post on X and reading X metrics work the same way, each with its own message.

A scheduled post that comes due when the balance is too low fails and is not retried on its own. Top up X credits, then send the post again. Connecting a new X account also stops until the balance covers one post.

A thread can run short partway, after its first parts went out. The part that ran short fails and the parts after it are not sent. Parts already up stay up. Top up, then call retry_post; it continues from this part. Do not send the whole chain again. The Retry button on the Posts page does the same.

Can I get my X credits refunded?

Yes, for unused X credits, if you ask within the refund period set in the Terms of Service. Press Contact at the bottom right of the dashboard and tell us which top-up you want refunded.

The payment processing fee is not returned, because the payment processor keeps it when a payment is refunded. Credits already spent on X are not refunded either, because Uplika has already paid X for that usage.

X sets a higher price for creating a post that contains a link than for a plain post, so Uplika's prices have a separate link price too, and a post whose text has a link is charged that link price.

X counts a link as an address that starts with http:// or https://. A bare domain such as uplika.com is charged as a plain post. The link price applies to a single post or the first post of a thread. A reply, which includes every post after the first in a thread, is charged the reply price with or without a link.

list_platforms carries Uplika's current X prices under pricing, and the dashboard settings show them too. To pay the plain price, leave the link out of the text.

Why can't I quote a post on X?

Uplika does not offer quote posts or likes on X. A request with a quote post is refused and nothing goes out.

Why can't I post the same text to two X accounts?

X's developer policy says not to post identical or substantially similar content across several accounts. Uplika posts to X through one app that every customer shares, so one breach could get that app restricted for everyone.

So when another X account of yours posted the same text in the last 24 hours, Uplika refuses with x_duplicate_across_accounts and nothing goes out. Extra spaces and line breaks, letter case and invisible characters do not make two texts different. Change the text for each account, then send it again.

Why can't Uplika show comments or numbers for my LinkedIn posts?

For a personal profile, LinkedIn lets apps write posts but not read them. The permission to read a member's posts, comments and reactions is closed: LinkedIn is not accepting requests for it.

So for LinkedIn, Uplika can publish, edit the text of a post it published, and delete it. It cannot list your posts, read comments, reply, or show views and reactions. Open the post on LinkedIn to see those.

To edit or delete a LinkedIn post through Uplika, point to it with the link or id Uplika gave when it was published. A link copied from LinkedIn (the one with activity in it) uses a different number that Uplika has no way to look up.

Naver Blog

Naver Blog posts are written by the Uplika browser extension (Chrome, Edge or Whale) in your own browser. If the browser with the extension is closed, the computer is asleep, or the extension is turned off in that browser, the post waits and goes out once the extension answers again. Uplika cannot always tell a closed browser from a turned-off extension: if the browser is open, check in its extension settings that Uplika is turned on. It waits up to seven days.

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

If you use the extension in more than one browser, the browser that is on may not have that blog's Naver login while the browser that has it is off. Then posts for that blog wait, and reading that blog's posts or comments is refused instead of running in a browser without the login. Uplika names the browser that is off. Turn it on, or press Open login window on the Connections page and log in to that blog's account in the browser that is on.

Uplika sends scheduled posts at the set time, but a Naver Blog post is written by the extension, so the browser with the extension has to be on, the extension turned on in it, and the computer awake at that time. If not, the post goes out once the extension answers again. When the extension is not answering an hour before a scheduled post, Uplika emails you.

Why hasn't the Uplika extension updated to the new version?

Your browser (Chrome, Edge or Whale) updates extensions on its own, when it starts and every few hours after that. So a new version can take a few hours to reach your browser after it is published. Once the browser has it, the extension switches to it by itself as soon as no Naver Blog work is running.

To move it along, press Update now on the extension badge at the top of the dashboard, on the Naver Blog card in Connections, or in the extension's popup. The button asks the browser to check right away. These browsers accept that request from an extension only about once every five hours, so when the button says the check is on hold, it cannot do more until then.

The direct way does not depend on that hold. Paste chrome://extensions (edge://extensions on Edge, whale://extensions on Whale) into the address bar, turn on Developer mode at the top right, and press Update. The browser fetches the new version at once, and you can turn Developer mode off afterwards. Quitting the browser completely and opening it again also clears the hold. Do either one when no Naver Blog post is going out, because Update does not wait for running work.

Do not remove and reinstall the extension to update it. Removing it deletes its pairing with Uplika and the Naver logins it saved on that computer.

Uplika sets no daily limit of its own on how many neighbors you add, comments you leave or likes you give on Naver Blog. Naver's own limits are the only ones, and Naver does not publish the numbers; its help page on managing neighbors has none. When Naver answers an add-neighbor request with a blank page, nothing was changed. A single blank page is answered as safe to send once more: in Uplika's records one blank page on 2026-10-11 was followed by a successful add six seconds later.

When the add-neighbor page keeps coming back blank on the same day (several times in a row, with no successful add in between), Uplika reads it as Naver limiting that blog's neighbor adds for the day. It stops sending adds from that blog until midnight Korea time and answers naver_engagement_limited with the time left; automations that add neighbors rest for the day too. In the one record of this (2026-10-13) a blog had added 99 neighbors that day, the page then came back blank six times, and a few hours later Naver asked that blog's admin pages to sign in again. Signing in again cleared it, and Uplika's usual login window handles that. When the blank page carries Naver's own refusal notice instead (that blog's neighbor count is over Naver's limit for mutual neighbors, or its owner has spam blocking set), that is the other blog's setting, not a daily limit: Uplika answers naver_follow_blocked, and such a request does not count toward the blank-page streak. A notice that this account's neighbor group is full is not a daily limit either: Uplika answers naver_follow_blocked and says to make room in that group, and such a request does not count toward the blank-page streak. When the blank page carries Naver's own notice that this blog has reached the number of neighbors it can add in a day, Uplika does not wait for a streak: that one notice stops adds from that blog until midnight Korea time. A notice that the other blog restricts neighbor relations is that blog's setting: Uplika answers naver_follow_blocked, and such a request does not count toward the blank-page streak either.

Most often it means the neighbor group Naver puts new neighbors in on your blog is full. Naver showed that notice on its add-neighbor page and did not add anyone. The group belongs to the blog doing the adding, so switching to another blog to add gives the same answer. Make room in that group on Naver (move some neighbors to another group or remove ones you no longer follow), then add again.

The other two refusals come from the other blog's settings: its neighbor count is over what Naver allows for mutual neighbors, or its owner turned on spam blocking. Sending the same request again gets the same answer, so pick a different blog instead.

You can also name another of your neighbor groups: an agent passes group to follow with the group's name as it appears on Naver, and the blog goes into that group instead. Uplika does not create groups. A name your blog does not have comes back as naver_follow_group_missing and nothing is clicked. An older Uplika extension answers extension_outdated to a follow with group, so update the extension first.

Both mean nothing was written to Naver. The extension looks for the comment before it opens the reply box or presses like, so when it cannot use the comment it stops there. Sending the same request again gives the same answer.

naver_comment_gone means the extension found the comment and Naver showed it as deleted. A deleted comment cannot be answered or liked; choose another comment. naver_comment_not_found means the comment was not in the comment list the extension could open. It may have been deleted, or it may be on a part of a long list that was not opened.

Naver shows a long comment list 50 items to a page, replies included, and opens it on the newest page. Extension versions before 0.7.37 looked only at that page, so on a post with more than 50 items a comment on an earlier page came back as not found (older Uplika servers called this deleted). Version 0.7.37 and later turn to earlier pages to find it, up to six pages back.

Open the post on the blog and check that the comment is still there. If it is and the extension is older than 0.7.37, update it and send the request again: Chrome updates extensions on its own within a few hours, and to update now, open chrome://extensions, turn on Developer mode and press Update. If the comment is there and the extension is up to date, let us know.

Uplika reads and acts on Naver Blog through the Uplika extension in your own browser (Chrome, Edge or Whale), and it waits for the answer for a set time: about a minute when reading your posts, drafts, comments or numbers, and two or three minutes when writing a comment, liking, adding a neighbor or deleting. When no answer comes in that time, Uplika answers bridge_timeout. A read changes nothing on Naver, so asking again is safe. A new comment, like, neighbor add or delete may still go through after Uplika stopped waiting, so check the blog before sending it again.

The usual reason is an account switch on hold. When one browser handles more than one Naver blog, the extension switches that browser's Naver login to the blog each task needs. While a Naver page is the open tab of the front browser window, it can hold the switch for up to five minutes so the login does not change under someone using Naver, and the tasks behind it wait too. Leaving that window on a page that is not Naver, such as a new tab, lets the switch happen at once. Other reasons: the extension is writing a post, which takes a few minutes, and reads wait behind it (ask again in a minute or two), or the browser was closing or the computer was going to sleep. When an agent edits several Naver posts in a row, have it edit them one at a time: each edit first reads the post from Naver, and that read waits behind the edits sent before it.

Sometimes the extension is connected but does not pick up the request at all. Uplika sends it once more after about 20 seconds, and if it still is not picked up the answer says the extension is connected but did not pick up this request. Click Reconnect in the extension's window (the Uplika icon in the browser toolbar), or restart that browser if it keeps happening, then ask again.

A queued post that no browser with the extension picked up within seven days also ends with bridge_timeout. Open that browser, then send the post again from Sent in the dashboard.

The Naver draft this post was saved as no longer holds it. Either Naver saved a later post into this post's draft instead of starting a new draft (Uplika saw the later post's title on this draft's number in Naver's draft list and gave the number to the later post), or the draft is no longer in the blog's draft list (a publish of that draft number failed because Naver did not list it). Uplika marked this post failed so it no longer points at a draft that does not hold it. Uplika did not delete anything on Naver.

The original text is still in Uplika. Open the post from Sent in the dashboard and try again: it is saved as a new draft. If the post is old, its photos may already have been cleaned up; then copy the text, upload the photos again and send it as a new post.

Edge itself refused to open a window for the Uplika extension: it answered "Window creation is restricted in standalone sidebar mode". Edge usually says this when its sidebar is attached to the Windows desktop as a standalone sidebar and every Edge browser window has been closed. Edge keeps running in that state, so the extension stays online and picks up tasks, but Edge does not let it open the window a Naver page needs. The extension is not turning anything off; Edge is blocking the window.

Open one Edge browser window and leave it open (or attach the sidebar back to Edge), then ask again. A read, such as listing a post's comments, changes nothing on Naver, so asking again is safe. A post that hit this did not go out at all: nothing was opened on Naver, an edit left the post unchanged and a draft is still in Naver's draft box. Send it again from Sent in the dashboard. A scheduled post needs an Edge browser window open at its scheduled time.

ChatGPT Atlas does not let extensions open new windows. The Uplika extension opens a window to write on Naver, so in Atlas it cannot write, save drafts or edit. Work that opens no window, such as reading the post list, still works.

Install the Uplika extension in Chrome, Edge or Whale, sign in to the same Naver ID there and keep that browser open. While it is on, that browser takes the work that needs a window.

Naver Clip posts belong to a clip profile, and a Naver account does not have one until the person makes it. Uplika does not make it for you: making a profile is a sign-up on Naver's side, and choosing to link a blog to it there cannot be undone.

Open Naver Clip Creators (clipcreators.naver.com) in the browser where the Uplika extension is installed, signed in to the same Naver account, and press Create profile. Then connect Naver Clip again under Connections. Nothing was uploaded.

Before uploading, the extension checks that the clip profile it connected is the one on the Naver account signed in for that blog. If it is not there (the profile was deleted or the connection points to another Naver account), it stops without pressing anything, so nothing goes to someone else's clips.

Connect Naver Clip again under Connections, then send the post again from Sent in the dashboard.

Naver Clip works through the same Uplika extension as Naver Blog, and only a newer version of the extension knows how to upload clips. An older version stays fine for Naver Blog.

Chrome updates extensions on its own within a few hours. To update now, open chrome://extensions, turn on Developer mode and press Update, then come back and connect Naver Clip again.

The extension uploads the video in Naver Clip Creators, fills in the fields and presses Post, then reads the clip list to find that video. As soon as the upload starts, Clip Creators keeps it as a draft, so a stop before Post can leave a draft in Clip Creators > Content.

If the upload stopped (fetching, uploading or encoding the video, adding the content link, or filling in the details), try again from Sent; you can delete the leftover draft. If the content link's post was not found in Naver Clip's blog search, nothing was uploaded; if that post was published in the last few minutes, send it again a few minutes later with the same link. If the page refused a field, the post says which one; fix it and send again. If Naver refused the Post request itself, the post says so with the HTTP status: nothing went up and the clip stays a draft, so press Post on that draft in Clip Creators > Content, or delete it and send a new post. If Post was pressed but the clip was not found, or the page did not answer after Post, check Clip Creators > Content first and send again only if it is not there, or it may go up twice. That is why Retry in Sent asks you once more, retry_post sends it again only with force: true, and for 10 minutes the same content answers duplicate_post.

Yes, to a post on your own blog. The Naver Clip Creators upload page has a Content link field, where Naver suggests adding links to Naver content related to the video, such as blog posts. Its Blog list offers only the posts of the blog on the same Naver account as the clip profile, so Uplika takes the address of one of those posts (an agent passes options.naver_clip.contentLink). The extension finds that post in the list, picks it and checks that it stayed on the clip. Clips saved as a Clip Creators draft get the link too.

Any other address is refused before anything is uploaded (naver_clip_link_invalid): a page that is not a blog post, the blog's home page, or a post on someone else's blog. If the extension cannot find the post in that list, for example because it was deleted or is on a different blog, or cannot tell it apart because another post on the blog has the same title, the clip is not posted; check the address and send it again, or send it without the link. If Naver Clip's blog search does not find the post, the clip is not posted either and nothing is uploaded (clip_rejected). A post published in the last few minutes can take a few minutes to show up in that search, so send the clip again a few minutes later with the same link. If the post is older, give it a title no other post on the blog has, pick another post, or send it without the link.

A clip posted from a clip profile does not appear on the blog linked to that profile. Naver shows content from a linked blog on the clip profile, but not the other way around, so this is how Naver works and nothing went wrong. Blog clips themselves can only be made in the Naver Blog mobile app.

That window was opened by the Uplika extension in your browser to write a Naver Blog post, and the extension closes it by itself when the post is done. A post with many large photos can take several minutes, and the window title shows how far it is (for example, photo 25 of 32). Please leave it open until it closes.

If the window is closed partway, that post does not go out (an edit leaves the post unchanged) and Uplika says so. Send it again from Sent in the dashboard or with retry_post and leave the new window open. A scheduled post needs the browser with the extension to be on at that time.

The diagnosis, the report card and the visibility scan read the blog's public feed (its latest post titles). Our server cannot read Naver's feeds right now, so the feed is read by the Uplika browser extension (Chrome, Edge or Whale) in your own browser.

If the error says the extension is offline and you have never connected it, connect Naver Blog on the Connections page (it installs and connects the extension), then try again; trying again without it fails the same way. If you have already connected it, the extension is not answering: open the browser it is in, or if that browser is open, check in its extension settings that Uplika is turned on, then try again in about a minute. If it says the extension is an older version, the browser updates it on its own once the new version is on the Chrome Web Store; you can press Update on the extension badge at the top of the dashboard to check.

If the extension read the feed and Naver still answered with an error, the blog id may be wrong, or the blog may have no public posts. A read that fails does not spend a diagnosis.

Why can a connection link not connect Naver Blog or Naver Clip?

Naver Blog and Naver Clip cannot be connected from a connection link, because their posts are written by the Uplika extension in the browser that connected them.

To connect a client's Naver account, sign in to Naver with the client's Naver ID in your own browser that has the Uplika extension, then connect it on the Connections page. Posts to that account then go out from that browser.

Agents

Why does Google keyword research answer google_keywords_busy or google_keywords_unavailable?

google_keywords_busy means the queue for Google's keyword data is full right now. The error says how many seconds to wait in retryAfterSeconds. Search again after that. If today's shared allowance has run out, that can be several hours.

google_keywords_unavailable means Uplika could not get the numbers from Google. There is nothing for you to connect or change. Try again a little later. If it keeps failing, tell us and we will look into it.

There is no daily search limit per person. Repeating a recent search returns the saved result right away, and asking for several keywords in one search instead of one search per keyword keeps you out of the queue.

Why does Meta or Google ad analysis answer ad_search_quota_exhausted, ad_search_busy or ad_search_unavailable?

ad_search_quota_exhausted means you have used today's ad analysis lookups. Meta ad analysis and Google ad analysis share one daily count. The error says how many you get a day in limit and when it opens again in resetsAt (midnight UTC). Repeating a lookup from the last 24 hours does not count, so ask the agent to reuse what it already found. Finding an advertiser and then reading its ads are two lookups, in both tools. On the dashboard, the button that shows an advertiser's other ads (inside a Meta ad's details, or the advertiser name on a Google ad) also counts as one.

ad_search_busy means Uplika's shared allowance for the ad data provider is used up for today. It opens again at the time in resetsAt (midnight Pacific time). There is nothing for you to change.

ad_search_unavailable means Uplika could not get ads from the data provider right now, or this server has no key for it. Nothing is connected to your account for these tools, so there is nothing to reconnect. Try again a little later. If it keeps failing, tell us and we will look into it.

These are other brands' public ads, from Meta's Ad Library or Google's Ads Transparency Center, not your own ad accounts. Neither shows spend or impressions here (Meta publishes them only for the EU, Google not at all), so how long an ad has been running is the signal.

The list Google ad analysis reads has no ad text. Each ad comes with the advertiser, the format, the days it was shown and a link to the original in Google's Ads Transparency Center. Open it with View on Google: the ad itself (text, image or video) shows there without a Google sign-in. An agent quoting an ad should show that link.

Google lists advertisers by their registered company, not by brand, and one company often has several advertisers. When a brand name finds nothing, search the company's legal name, or type the website (for example oliveyoung.co.kr) to see every ad that sends people to that site.

A website's results also include resellers, partner brands and ad agencies that send ads there under their own names. Pick one advertiser in the chips above the cards, or press an advertiser's name on a card to see only that advertiser's ads.

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. Over REST you also get it when the x-uplika-workspace header names a workspace that is not on your account (or not in the API key's scope), or one that was deleted. If you did not say which workspace, your agent asks you; once you answer, it keeps using that one for the rest of the conversation. Over REST, pick one from the list in the error and call again.

Why does my agent get account_required?

The call works on one connected account and nothing said which one. The error lists the accounts it could mean in accounts. Pass accountId with one of them and call again. Uplika does not pick one for you, because a wrong guess would act on another account.

On a post that went to several channels it means the same thing. One post can go out on several channels, and each channel has its own copy with its own comments. A reply, hide, delete or like has to land on one copy, so Uplika needs to know which. It reads the accountId you pass, then the channel link you gave as the post, then whose comment you are replying to (a reply id Uplika knows, such as a triggerRef from an automation run). If none of these says which copy, or two of them point at different copies, nothing is sent and you get account_required with the accounts that hold a copy. Channels that cannot do that action are left out of the list and the message says why.

Pass accountId with one of those accounts, or the link to that channel's copy, and call again. Reading replies or metrics without either still works: the answer says which copy was read in accountId and platform, and lists the others in otherAccounts. Send the reply with that same accountId.

Why does my agent get post_spans_channels when it deletes or edits a post?

The post was named by a channel link or by one channel's own post id, and the post also went out on other channels. Deleting a post removes it from every channel it went out on, and editing a published post rewrites it on every channel. A link only points at one channel's copy, so Uplika stops before calling any channel. Nothing was deleted or changed. The error lists the channels the call would have reached in channels, and the Uplika post id in postId.

Check with the person which they meant. To remove or change only one channel's copy, do it directly on that channel. To delete or edit the post everywhere, send the same call with the postId from the error. Naming the post by its Uplika post id always means the whole post.

ChatGPT does not show a new Uplika tool. What do I do?

ChatGPT keeps the list of Uplika tools it received when you connected, so a tool Uplika added or changed later is missing there until you refresh the list. Open the Uplika connection in ChatGPT Plugins and select Refresh, then start a new chat. These names were checked on a personal free ChatGPT account and in OpenAI's documentation, and other plans may show them differently.

Refreshing does not disconnect Uplika. Your connected channels, automations and posts stay as they are.

How do I get an image from ChatGPT into Uplika?

In ChatGPT, Uplika takes files from the conversation through the media_from_file tool. Attach the image to the chat, from your computer or from your ChatGPT library, and ask ChatGPT to post it with Uplika. Uplika downloads the file, stores the bytes unchanged and gives ChatGPT a media id to publish with. ChatGPT's code runtime often cannot reach Uplika's upload address, so the media_presign route does not finish there.

Images ChatGPT made in the conversation and files it made with code come through the same tool when ChatGPT passes the file's path (it starts with /mnt/data/). If ChatGPT passes only a file id, Uplika receives text instead of a file and refuses it, and nothing is stored. A very large file such as a long video can take longer to download than Uplika allows; the upload link (media_upload_link) lets you upload it from your device instead.

If ChatGPT does not see media_from_file, open the Uplika connection in ChatGPT's settings and refresh its tools there. ChatGPT keeps the tool list from when you connected until it is refreshed.

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.

Codex sign-in stops with missing required issuer. What do I do?

You approve Uplika in the browser and the page says you are signed in, but Codex stops with Authorization server response missing required issuer. Uplika does put the issuer (iss) in the address it sends back to Codex.

Codex 0.143 to 0.146 dropped that value and then stopped because it was missing. Codex releases after those fixed it.

Update Codex to the latest release, then run codex mcp login uplika again. If the same error comes back, this computer may have two copies of Codex installed. Update the one that actually runs when you type codex.

How do I tell the Uplika team about a problem?

Press Contact at the bottom right of the dashboard, or ask your agent to tell the Uplika team. The agent shows you what it will send first, and the reply goes to the email on your Uplika account.

The same problem is emailed to the team once in 24 hours, and a repeat is still recorded. An agent can send up to 5 reports a day for one account. When those are used up the agent gets support_daily_limit, and Contact in the dashboard still works.

My agent says the Analytics allowance is used up

Google gives each GA4 property an allowance per hour and per day, and other tools that read the same property use the same daily allowance. Uplika also stops a little before the daily one runs out, so those tools keep working.

The scope field says which one ran out, and a daily one carries resetAt. An answer with propertyQuota shows what is left. A shorter date range and fewer dimensions use less of it, and the same report asked again soon after comes from a copy and uses none.

Google rejected an Analytics report request

The reason field says what to change. Usually it is a metric or dimension name this property does not have, or a metric and a dimension that cannot go together. get_analytics_metadata lists the names this property has.

The same request gets the same answer, so change it first. Realtime reports accept fewer names than get_analytics_report does.

Google Analytics did not answer

Uplika could not get an answer from Google Analytics for this read. Your connection did not change, so there is nothing to reconnect. Try again in a few minutes.

Google Ads

Why can't my agent turn on an ad or raise its budget?

Turning ads on and raising budgets can spend real money, so they only go through inside a daily budget cap that a person set in the dashboard. Agents cannot change the cap. ad_budget_cap_unset means no cap is set yet: set an amount, or choose No limit, on the ad account card (Google Ads or Meta Ads) under Connections. With No limit, turning on and raising skip the check against the total, and one raise still goes up to 2 times the current amount at most.

ad_budget_cap_exceeded means the daily budgets of the account's enabled campaigns would pass the cap. It counts what the ad network has right now, including campaigns people turned on in its own ads manager. cap, wouldBe and currency in the answer say by how much. Raise the cap, or pause or lower another campaign. Pausing and lowering always go through.

ad_budget_unreadable means the ad network gave no daily budget where Uplika needs one: for the campaign being raised (to apply the raise limit), or, when a cap is set, for a campaign in the account (to add up the total). Make that change in the network's own ads manager. On Meta this happens when a campaign or ad set has a lifetime budget instead of a daily one. ad_status_superseded means a pause for the same ad arrived while turning it on waited, so it stays off: send it again if you still want it on.

Why was this budget increase refused?

One change can raise a campaign's daily budget up to maxRatio times its current amount, even inside the cap. The limit keeps one wrong number from multiplying spend.

For a larger increase, raise it in steps, or change it yourself in the ad network's own ads manager.

The ad network says this ad account can no longer be reached

On Google Ads, the Google account you connected with has lost access to this ad account, or to the manager account above it. On Meta, the person or system user that connected it was removed from the ad account, or from the business portfolio that owns it. Reconnecting with the same login does not help until that access is back.

Give that access back in Google Ads or in the Meta business portfolio, then repeat the request. The connection recovers by itself once a request succeeds. On Meta, someone who still has access to the ad account can also reconnect it under Connections. To use another ad account, disconnect this one and connect the other.

The ad network says today's allowance is used up

On Meta, ads_quota_exhausted means Meta itself slowed reads or changes on the ad account for a while, not Google's daily operation quota. Wait for retryAfter. Uplika's own per-object and per-hour limits answer ad_rate_limited instead, which has its own entry.

For Google Ads: Uplika's Google Ads API allowance is shared, each workspace has its own share of it, and both reset at midnight Pacific time. retryAfter in the answer is that moment. Until then, reads and writes stop. list_ads keeps a small reserve so you can still find the id of an ad to turn off.

Uplika's own count never blocks pausing: set_ad_status with PAUSED still goes through if you have the id. Google can still refuse at its own daily limit. Then the ad stays on and list_ads stops too. To be sure, turn it off directly in Google Ads.

Google Ads says Uplika's access does not cover this account

Google has limited what Uplika's Google Ads API access can reach. This is on Uplika's side. Reconnecting or changing anything in your account will not change it.

Nothing was changed in your ad account. Tell the Uplika team if you see this.

Google Ads or Meta rejected this request

The ad network refused the request as sent, for example a campaign name already in use, a headline too long, or an ad policy. The answer carries the network's own reason: googleErrors from Google Ads, metaError from Meta. Nothing that can run was kept. If Meta refused a step after Uplika had made a paused campaign for a post, Uplika deleted it, and leftovers lists any it could not remove.

The same request will be refused again. Change what the network's message names first. validateOnly checks with the network without creating anything: on create_ad_campaign for Google Ads, and on boost_post for Meta, where it checks the campaign and the creative.

Google Ads or Meta did not answer

The ad network failed or was too busy, and Uplika's own retries ran out. If this was a write, it may or may not have reached the network.

Read list_ads before repeating a write. If the campaign is there, it was created, and new campaigns are always paused, so creating one moves no money. If you were turning an ad on or raising a budget, the change may already be live, so check its status first.

My agent says this workspace has more than one ad account connected

When a workspace has both a Google Ads account and a Meta ad account connected, get_ad_account, get_ad_insights and list_ads need to know which one to read. ad_provider_required comes with candidates: each connected account's network, account id and name.

Send the same request again with provider set to google_ads or meta_ads. If the person did not say which one, ask them instead of picking one. With only one ad account connected, provider is not needed.

My agent says this ad id was not found or does not belong to that network

ad_object_not_found means nothing was read or changed, for one of three reasons. On set_ad_status and update_ad_budget, provider named one network and the id belongs to the other: a Google Ads id looks like customers/1234567890/campaigns/111 and a Meta id is digits only, so leave provider out and let the id decide. On Google Ads tools such as get_ad, the id names a different Google Ads account than the one connected to this workspace. Or Google Ads has no such object in the connected account, usually because someone removed it in Google Ads or the id was copied wrong.

Read the ids again with list_ads, or with get_ad on the campaign or ad group above it, and use those. A keyword removed through Uplika reads back as removed: true instead of this error. If the person meant an ad on the other network or in another Google Ads account, connect or pick that account first.

My agent says this Google Ads connection has not accepted what Uplika can now do

Uplika can now do more in Google Ads than when this account was connected: remove and edit search campaigns, ad groups, ads and keywords, add ad groups, ads and keywords to existing campaigns, create Demand Gen and display campaigns with images and videos, and create Performance Max campaigns. A connection made before those were added has not agreed to them, so those tools answer ad_terms_update_required and nothing is read or changed.

The person who owns the workspace opens Connections in the Uplika dashboard, reads the list on the Google Ads card and presses Accept. An agent cannot accept for them. Pausing, lowering budgets and the tools that worked before keep working until then. After accepting, send the same request again.

Removing a campaign, ad group, asset group, ad set, ad or keyword in Google Ads or Meta

Removing in Google Ads cannot be undone, and neither can deleting in Meta. A removed campaign, ad group, ad or keyword cannot be turned back on, edited or given new ad groups, ads or keywords, and the same goes for a deleted Meta campaign, ad set or ad. In Meta, deleting a campaign or an ad set also deletes everything under it. To stop spending for now, pause it instead.

To remove a campaign, an ad group or a Performance Max asset group in Google Ads, or a campaign or an ad set in Meta, the agent first reads its current name with get_ad and sends that name exactly as confirmName. If the name does not match, the request is refused with ad_confirm_name_mismatch and nothing is removed. Without confirmName the answer is invalid_params. Uplika does not show the current name in that answer, so the agent has to read it again and say what it is about to remove. Ads and keywords are removed without a name, and so are Meta ads.

Countries are not removed this way. Change them with update_ad_campaign, which keeps at least one country, because a Google Ads campaign with no country shows ads everywhere.

If something was already removed, by you earlier or by someone in Google Ads or Meta Ads Manager, the answer says alreadyRemoved and nothing more happens. In Meta an archived object counts as removed too. If an edit or a new ad group, ad or keyword is refused with ad_object_removed, the object or its parent was removed in Google Ads. In Meta, ad_object_removed means the campaign, ad set or ad, or the one above it, was deleted or archived, and get_ad on it answers the same. Make a new one instead.

Turning on a Meta campaign or ad set that Uplika created also turns on the paused ad sets and ads Uplika created under it, except ad sets and ads last turned off through Uplika: those stay off, and so do the ads under such an ad set. If one that would be turned on was deleted in the meantime, turning on stops with ad_object_removed and the one you asked for stays off; enabled lists any that were already turned on. The answer does not say which one was deleted, so read it again with get_ad, or with list_ads, before turning it on again.

Changing the bid strategy or max CPC of a Google Ads campaign

set_ad_bidding switches a campaign between three bid strategies: Maximize clicks (MAXIMIZE_CLICKS, with an optional max CPC), Maximize conversions (MAXIMIZE_CONVERSIONS, with an optional target cost per conversion) and Maximize conversion value (MAXIMIZE_CONVERSION_VALUE, with an optional target ROAS). Changing only the target uses the same tool. A target ROAS is a ratio, so 3.5 means 350%.

A max CPC (the most a click may cost) exists only with Maximize clicks. update_ad_campaign can set or clear it on such a campaign. On another strategy it is refused with ad_bidding_not_supported and nothing is changed. Change the strategy with set_ad_bidding first.

Not every campaign type takes every strategy. Performance Max bids for conversions only. Demand Gen takes no max CPC, because Google does not accept a click price ceiling there. Other types, such as Video and Shopping, are changed in Google Ads. These also answer ad_bidding_not_supported.

After a change Google adjusts over one or two conversion cycles, so results can move around for a while. Leaving Maximize clicks drops the max CPC, and the answer's dropped gives the old value so you can put it back. The daily budget still limits what the campaign spends.

Which images and videos Google Ads campaigns take

Demand Gen, display and Performance Max ads take images you uploaded to Uplika (their media ids) and YouTube videos. Each image slot has a fixed shape: landscape 1.91:1 (at least 600脳314), square 1:1 (at least 300脳300), portrait 4:5 (at least 480脳600), tall portrait 9:16 (Demand Gen image ads only, at least 600脳1067), logo 1:1 (at least 128脳128) and landscape logo 4:1 (at least 512脳128). Images are JPG, PNG or GIF up to 5,120KB.

Creating a campaign never crops or stretches an image on its own, because the ad should show the picture you chose. If an image does not fit its slot, the request is refused with ad_media_unfit before anything is sent to Google, and the answer lists every image that did not fit, with its slot and measured size.

fit_ad_images makes a copy in the right shape. Photo slots are cropped around the middle of the picture, or at the top, bottom, left or right if you ask. auto keeps the brightest, most colourful part instead, which can miss faces, so look at each copy and ask again with another position when something important was cut. Logo slots get a transparent margin instead, so letters are not cut. Each copy is a new media id with a link to look at first, and the original stays as it was. Uplika never enlarges a picture, so one smaller than the slot's minimum needs a larger original.

Videos can be a YouTube video id, a YouTube link, or the publish id of a post that Uplika published to YouTube from the same workspace. A video file takes two steps: publish it to your YouTube channel as unlisted, then put that post's publish id in the video field. The same refusal comes back when a video reference cannot be read. Google may still refuse a video id that does not exist.

Images from another workspace cannot be used.

Google's minimum daily budget for Demand Gen campaigns

Google sets a minimum daily budget for Demand Gen campaigns, and it differs by currency. Uplika reads it from Google before creating the campaign. If the budget is lower, the request is refused with ad_budget_below_minimum and the answer carries the minimum and the currency. Nothing is created.

Lowering the budget of an existing Demand Gen campaign below the minimum is refused the same way, and the budget stays as it was.

Your own daily budget cap is checked when a campaign is turned on, not when it is created. Campaigns are always created paused.

Why bidding for conversions needs a conversion signal

Performance Max campaigns and the Maximize conversions and Maximize conversion value strategies bid for conversions (sign-ups, purchases and the like). Without a recent conversion Google has nothing to learn from and spends the budget without a signal. So before creating a Performance Max campaign or switching a campaign to a conversion strategy, Uplika checks the last 30 days. If no enabled conversion action that bidding counts recorded a conversion, the answer is ad_conversion_tracking_missing.

The reason in that answer says what is missing. no_action: the account has no enabled conversion action, and create_conversion_action makes a website one and returns its tag. no_recent_conversions: there are conversion actions, but none counted for bidding recorded a conversion in the last 30 days. Check that the tag is on the site and try again after the first conversion is recorded. google_not_enough: Uplika's check passed, but Google says there are not enough conversions yet for that strategy.

Uplika does not put the tag on your site. A person or an agent adds the global site tag to every page and the event snippet to the conversion page. Switching to Maximize clicks needs no conversions.

Meta shows my ad account as not active

Meta marks an ad account as not active when it is disabled, closed or about to close, has an unpaid balance, or is under review. Its ads may not be delivering. get_ad_account shows Meta's status number in accountStatus, and Meta's reason in disableReason when it gives one.

Uplika still reads a not active account, so your agent can look at its past numbers. Turning ads on, changing budgets and boosting posts are refused with ads_account_disabled, and nothing is changed. Turning ads off still works.

Fixing it happens in Meta, not in Uplika: a person opens the ad account in Meta Ads Manager and does what Meta asks there. Once Meta shows the account as active again, the same request goes through.

My agent says the Meta connection was made for reading only

A Meta ad account connects for reading first. Turning ads on or off, changing budgets, boosting posts, and creating, changing or deleting campaigns, ad sets and ads need management as well, which a person allows separately. ads_write_not_granted means this connection does not have it yet, so nothing was changed.

Under Connections in the dashboard, press Allow management on the Meta Ads card of that workspace. Meta asks once more, this time for managing ads and for the Pages and Instagram accounts to use in ads. Then set a daily budget cap on the card. If the account is later connected again without Allow management, management ends and these requests answer this code again.

My agent says Meta is limiting changes to an ad

Uplika sends at most one change to the same campaign, ad set or ad every 30 seconds, because Meta refuses changes that come faster. Meta allows 4 budget changes per hour on one campaign or ad set, and can also slow down changes on a whole ad account for a while. ad_rate_limited means one of these limits was reached, so nothing was changed. limit says which one, and retryAfterSeconds says how long to wait.

Send the same request again after that time. If the request was to turn something off, it is still on and still spending until then. To stop it at once, a person turns it off in Meta Ads Manager.

My agent says the Meta connection cannot see pixels

ad_pixel_access_missing means Meta did not show any pixel to this connection, so the list could not be read. Nothing was changed.

Under Connections in the dashboard, reconnect the Meta Ads card of that workspace. In Meta's dialog, pick the pixel (dataset) you want to use, then ask for the list again.

Why the pixel numbers differ from Ads Manager

The Pixel section of the Ads tab shows two different numbers. Events the pixel received counts everything the pixel saw on your site, whether or not an ad led to it: a visit from search, an email link or someone typing the address all count. Conversions credited to ads counts only what Meta credits to your ads, and Ads Manager reports that one. Do not add the two, and do not expect them to match.

Credited conversions are counted inside an attribution window, such as a click window or a view window, so the same purchase can be credited to an ad in one window and not in another. Ask for the windows with attributionWindows on get_ad_insights together with breakdownByConversion. get_meta_pixel_stats returns only the events the pixel received, per day in the ad account's time zone, web and server apart, per event name.

Meta does not provide individual events, so there is no list of who did what and when. Only counts come through: per day and per event name, and for recent days also by page address, device, browser and similar groupings, which pass through without being stored. Days Uplika has not stored, including days its daily read missed, are listed as not collected, not shown as zero.

My agent says the pixel is not shared with the Meta connection

ad_pixel_not_shared means the pixel the agent picked, to read its numbers or to use in a new Meta campaign, is not one this connection can use, or Meta marks it unavailable. Uplika read the pixel list again before answering, and read or created nothing with that pixel.

Under Connections in the dashboard, reconnect the Meta Ads card of that workspace. In Meta's dialog, pick the pixel (dataset) inside the business portfolio that owns the ad account. Then have the agent check list_meta_pixels and try again.

My agent says the budget is on another level of the Meta campaign

In Meta a daily budget sits either on the campaign or on each of its ad sets, not on both. update_ad_budget changes the budget where it sits, so the id has to be that object. ad_budget_level_mismatch means the id pointed at the other level, and nothing was changed.

budgetOn says where the budget is: campaign, or ad_group, which is Meta's ad set. ids lists the ids to use. Send the change with one of those ids. When the budget is on the ad sets, each ad set has its own, so pick the one the person means or ask them.

My agent says this post cannot be boosted

boost_post turns a published Facebook Page feed post or Instagram post into a paused Meta ad. ad_post_not_boostable means this post cannot be used, and nothing was created. reason says why: not_published (it has not gone out, or publishing failed), deleted, facebook_not_feed_post (Facebook reels, stories and videos), instagram_story, channel_not_supported (only Facebook and Instagram posts can be boosted), or meta_refused (Meta says the post is not eligible right now, and meta has Meta's own answer).

Pick another published post. For meta_refused, what Meta said in meta is what has to change first, so sending the same post again gets the same answer until then.

My agent says the Page or Instagram account is not shared with the Meta connection

To use a post in an ad, the Meta connection needs the Facebook Page or Instagram account the post is on. Those are picked in Meta's dialog when management is allowed. ad_post_not_shared means the post's Page or account was not picked, so Meta would not use the post. platform in the answer says which kind it is. Nothing is left running: if Uplika had already started a paused campaign for this boost, it deleted it, and leftovers lists any it could not remove.

Under Connections in the dashboard, press Reconnect on the Meta Ads card. In Meta's dialog, pick the business portfolio that owns the ad account, then pick that Page or Instagram account. Then boost the post again.

My agent says the Meta ad account has no payment method

Meta does not create or change ads in an ad account that has no payment method. ads_payment_method_required means Meta refused for that reason, and nothing is left that can run. If it happened while boosting a post and Uplika had already started a paused campaign, it deleted it, and leftovers lists any it could not remove.

Only a person can add a payment method, in Meta. When boost_post gives this answer, paymentUrl opens the payment settings of that ad account in Meta. Otherwise open the ad account in Meta Ads Manager. Uplika never adds or changes payment methods. Once one is added, send the request again.

My agent says the image or video for a Meta ad was refused or is still processing

A new Meta ad creative is made from media uploaded to Uplika in the same workspace, when creating an ad with create_meta_campaign, create_meta_ad_set or create_meta_ad, or when changing an ad's creative with update_meta_ad. To make the creative, Uplika uploads the images to Meta, and for a video gives Meta the file's address so that Meta fetches it.

How many media ids a creative takes is checked first: an image ad takes one, a video ad one, and a carousel two or more, one per card. Another number answers invalid_params, with field pointing at mediaIds. ad_creative_media_invalid means a media file itself does not fit, and the answer's reason says which rule it broke: an image ad and carousel cards take JPEG or PNG images, a video ad an MP4 or MOV video. Uplika does not crop, resize or convert, so an image over the size limit or a file that is not a readable JPEG or PNG has to be uploaded again in a form that fits. A media id that is not ready, or that belongs to another workspace, gets the same answer. It also comes when Meta could not process a video: upload a different MP4 or MOV file. No ad was created or changed.

ad_creative_media_processing means Meta is still processing the video. Nothing was created or changed. Send the same request again after the seconds in retryAfterSeconds.

My agent says the Facebook Page for a Meta ad is not shared

An ad runs from a Facebook Page: the Page on a new creative, or the Page that receives messages or instant forms for an ad set. ad_page_not_shared means that Page is not shared with this workspace's Meta Ads connection, so Meta would not run an ad from it. It can also mean an Instagram account is not the one connected to that Page: the instagramAccountId on any new creative, or, for an ad set that sends Instagram messages, the account of the post used. field says which.

Reconnect the Meta Ads card in the dashboard and, in Meta's dialog, pick that Page inside the business portfolio that owns the ad account. For the Instagram case, send the Instagram account connected to that Page, or pick it in the same dialog. Then send the request again.

Uplika checks this before writing anything when it can. If Meta refused only after Uplika had started a paused campaign or ad set for this request, Uplika tried to delete it, and leftovers lists any that are left.

My agent says a field cannot be set on a Meta campaign, ad set or ad

When creating or changing Meta ads, Uplika does not take the fields that turn spending on or decide how much is spent. ad_field_not_editable names the field it refused in field, and nothing was created or changed.

Status is not set here: everything Uplika creates starts paused, and set_ad_status turns it on or off. Turning on has to fit the daily budget cap, unless a person chose No limit for it. A daily budget that already exists changes with update_ad_budget. Lifetime budgets, spend caps and spend targets, bid strategies and bid amounts, pacing, budget schedules and budget sharing between ad sets are left to a person in Meta Ads Manager.

When changing, the same code comes for a field that belongs to another level, for example targeting on a campaign; the reason lists the fields you can send. It also comes when adding an ad set with dailyBudget to a campaign that keeps its budget on the campaign: leave dailyBudget out there.

My agent cannot change the start or end time of a Meta campaign or ad set

A lifetime budget is spent over the dates it runs, so moving the dates changes how fast it is spent. When the campaign or ad set runs on a lifetime budget, on itself, on the campaign above it or on an ad set under it, Uplika does not change its start or end time, and that includes clearing the end time. ad_lifetime_budget_unsupported means nothing was changed.

The same refusal comes when a campaign has more ad sets under it than Uplika reads at once: Uplika cannot confirm that none of them runs on a lifetime budget, so it refuses the schedule change for the same reason.

Changing the name still works. A person changes the schedule in Meta Ads Manager. Uplika itself creates only daily budgets.

My agent says Meta ad targeting was refused or could not be read

A campaign that declares one of the special ad categories HOUSING, EMPLOYMENT, CREDIT, FINANCIAL_PRODUCTS_SERVICES cannot narrow who sees its ads the usual way: Meta does not allow choosing genders, zip code targeting, a city radius under Meta's minimum, or narrowing the age range. ad_special_category_conflict names the targeting field in field. Nothing was created or changed. Remove that part of the targeting and send the request again. Other special ad categories do not limit targeting this way. The categories come from the campaign, so an ad set added to an existing campaign follows them too.

ad_targeting_unreadable means Meta did not return what Uplika has to check first: the ad set's current targeting or its campaign when changing targeting, or the campaign's objective or special ad categories when adding an ad set. Uplika does not change targeting without it, because that could overwrite the rest of the targeting or let through targeting the categories forbid. Nothing was created or changed. Try again, or a person makes the change in Meta Ads Manager.

My agent says a Meta ad set that reaches the EU needs a beneficiary and payer

Meta needs a beneficiary (who the ad benefits) and a payer (who pays for it) on any ad set whose targeting reaches the EU. Uplika does not make these up. It keeps the values the ad set already has and fills only what is missing from the defaults set on the Meta ad account. ad_dsa_required means neither had them, and nothing was created or changed.

When creating a campaign or adding an ad set, the agent can send dsaBeneficiary and dsaPayor; field says which one is missing. Otherwise, and when changing an ad set's targeting, a person sets a default beneficiary and payer on the ad account in Meta Ads Manager. Then send the request again.

Reading this from an agent

get_help takes code (an error code), query (a few words in any language), id, platform and locale. Without arguments it lists every question. Over REST, the same answers are at GET /v1/help, with no key needed. When the answer is something to do on a screen, it also has manual: the step-by-step manual page in that language. Answers without one leave the field out.

GET/v1/help

Troubleshooting answers by error code, question or id. No authentication.

Query parameters

NameTypeDescription
codequeryAn error code, e.g. reconsent_required. Returns the answers for that code.
qqueryA short question in any language. Returns the five best matches.
idqueryOne answer by its id, e.g. thread-control.
platformqueryOnly answers about this platform, plus general ones.
categoryquerydm, connect, publish, naver or agent.
localequeryen (default) or ko.
curl "https://api.uplika.com/v1/help?code=reconsent_required"