Troubleshoot the workflow, not just the last screen
Most problems become easier when you identify the stage that failed, preserve the useful work, and check the prerequisite immediately before that stage.
10 min · Last verified 11 August 2026
Start here
- Name the stage: connection, generation, review, schedule, delivery, inbox, or analytics.
- Preserve the work: keep the draft, asset, prompt, delivery error, and destination account visible.
- Read the product state: distinguish a draft from approved content, a scheduled post from a published one, and a delayed metric from a missing connection.
- Check one prerequisite back: account access, remaining credits, approval, media requirement, or network permission.
- Retry once after correction: repeated retries do not solve an unchanged prerequisite.
The original item keeps the approval, schedule, destination, and failure history together. Fixing that item is usually safer than producing a duplicate.
A social account will not connect
- Confirm you are signing into the intended network account.
- Confirm that account can administer the target Facebook or LinkedIn Page.
- For Instagram, confirm the account is Business or Creator and linked to a Facebook Page.
- Accept the permissions Vuti needs for the chosen workflow.
- If the network returned to Vuti without the account, reopen Connected Accounts and retry once.
Generation is unavailable or stops
- Check Settings → Usage & credits for the current balance and plan access.
- Reduce the requested number of outputs while exploring a direction.
- For video, confirm the quoted cost before starting and watch the asynchronous job state instead of starting another render.
- If a failed job was eligible for a refund, allow the reservation and refund state to settle before trying again.
- If repeated outputs miss the same voice requirement, improve the brand and voice context instead of regenerating unchanged instructions.
A post cannot be scheduled
- Confirm the post has been approved in Vuti, not only discussed in a comment or external message.
- Confirm it has at least one connected destination account.
- Confirm the schedule is in the intended workspace timezone and still in the future.
- Check whether the selected media and format are valid for each destination.
- On Free, check whether the monthly scheduled-post limit has been reached.
Publishing failed
- Open the failed delivery from Today or the post’s delivery history.
- Read the network response and note which destination failed.
- Reconnect the account if the error refers to authorization or permissions.
- Correct media, length, account type, or format requirements when named.
- Retry the failed destination after the correction.
Do not republish destinations that already succeeded when a multi-channel post only failed on one network.
Inbox actions or analytics are missing
First confirm the account is connected and has completed its latest sync. Then remember that inbox and analytics depth varies by platform, account type, permissions, and the data the network exposes.
- A field unavailable for one platform does not necessarily mean the entire sync failed.
- Recently published content may take time to appear in third-party metrics.
- Reconnect when Vuti explicitly reports expired or reduced permissions.
- Use delivery history to verify publishing independently from analytics availability.
Ask support with useful context
Include the workspace name, affected platform, post or job title, approximate time, stage that failed, exact visible error, and what you already tried. Do not send social-network passwords, access tokens, billing card details, or confidential source material by email.