# Troubleshooting > The problems that actually come up, and what to do about them. Source: https://advibly.com/docs/reference/troubleshooting Start with the exact structured error returned by the tool. Preserve its `error` code, message, and relevant id; those decide the branch below. Change one variable per retry so the result identifies the cause. ## A generation was rejected [#a-generation-was-rejected] Content moderation declined it, and your credits were refunded. The filters are stricter than the subject matter suggests. Swimwear, underwear and skin-heavy product categories trip them routinely, even for ordinary catalogue photography. **What works**: stage the product without a person in the frame - flat-lay, on a hanger, in an empty room. You usually get the shot you wanted, and it is often a better product ad anyway. ## A generation failed [#a-generation-failed] The model provider errored. Credits were refunded; re-submitting is free and usually works. If it fails repeatedly, change one thing at a time - first the model, then the size or duration. Unusual dimension and duration combinations are the most common cause. ## It has been processing for a long time [#it-has-been-processing-for-a-long-time] Video legitimately takes minutes. Heavy image settings - the highest quality tier, a large size, and several brand references together - occasionally take five minutes or more. Re-submitting does not cancel the first attempt, and you pay for both. If you are past five minutes on an image, re-submitting at `medium` quality is usually faster than continuing to wait. ## The output ignored my brand [#the-output-ignored-my-brand] Two different things get confused here: * `brand_id` decides where the generation is **filed**. * `on_brand` decides whether brand **styling** is applied. A generation with brand styling off is still filed under the brand. Check the `on_brand` argument sent to the MCP tool. If styling is on and the output still looks wrong, the brand itself is probably wrong. Call `advibly_get_brand` to inspect its identity and `advibly_view_brandkit` to inspect the rendered brand kit. ## The text in my image is gibberish [#the-text-in-my-image-is-gibberish] Write the literal words in quotes inside the `prompt`, spell the brand name exactly, and say where the text belongs in the composition. ## My agent cannot connect [#my-agent-cannot-connect] Work through it in this order: 1. Call `advibly_check_credits` with a valid `context` - it proves tool access without starting a generation. 2. If it 401s, sign in again from the client. Tokens expire. 3. Confirm the URL is exactly `https://advibly.com/mcp`. 4. Confirm the transport is Streamable HTTP, not SSE or stdio. If discovery works but the call rejects `context`, send a 15–25 word, third-person explanation of how the call supports the user's goal. Do not put credentials or personal data in it. ## An agent says a brand does not exist [#an-agent-says-a-brand-does-not-exist] Call `advibly_list_brands` and use an id from the response. Brand ids are not guessable, and an agent that invented one will get this error. The same rule applies to products, projects, profiles, posts, actors, assets, and generations: resolve ids from a list or create response in the signed-in account; never infer them from names. ## The account has insufficient credits [#the-account-has-insufficient-credits] Call `advibly_check_credits` to confirm the balance, then `advibly_buy_credits` to retrieve current packs and checkout links. Share the link and stop the billable branch. Credits apply after payment; resume from the first generation that did not run rather than repeating completed work. ## A local upload returns `403` [#a-local-upload-returns-403] Create a new presigned URL using the file's exact MIME type and byte length, then `PUT` the unchanged raw bytes. A different body size invalidates the signature. After the upload succeeds, call `advibly_upload_asset` with the returned `upload_key`; the `PUT` alone does not add the file to the library. ## A post did not publish [#a-post-did-not-publish] Call `advibly_social_list_accounts` for the brand. If the target profile is missing or disconnected, its network authorisation must be renewed before MCP can publish to it. A failed post can be retried without recreating it. ## Still stuck [#still-stuck] [Advibly support](https://advibly.com/support).