Troubleshooting
If you’ve seen an error message and you want to know what to do about it, this is the page.
For “how does X work” questions, see the FAQ or the topic-specific docs. For something that isn’t covered here, open the in-app support widget.
Generation errors
”The AI model is busy — please try again in a minute”
The AI provider is rate-limited or temporarily congested. This is most common during peak hours on a popular provider.
What to do: Click Retry. If it fails again after 60 seconds, wait a few minutes and try once more. The error is transient and self-resolving.
Will I be charged for this? No. Failed generations don’t count against your transformation quota.
”AI declined — content flagged”
The AI provider’s safety filter blocked the generation. This usually triggers on:
- Controlled substances (some categories of supplements, cannabis-related products)
- Weapons or weapon accessories
- Certain medical or therapeutic claims
- Adult content
What to do: Open your original Shopify product description and look for trigger words. Rewording the original (or removing specific claims) often resolves it. On Pro, you can also try Settings → Quality controls → Override model to switch to a model with different filter behaviour.
If you sell in a category that’s consistently triggering filters, contact support — we can route your store to provider configurations better suited to it.
”Generation timed out”
The AI took too long to respond and we gave up to avoid hanging the page. Common on very long product descriptions or during provider congestion.
What to do: Retry. If your original description is unusually long (over ~3000 words), consider shortening it before styling.
Will I be charged? No.
Quota errors
”Quota reached for this cycle”
You’ve used your monthly transformation budget. New manual generations are blocked until the next cycle reset.
What to do:
- Wait for the next cycle (check Settings → Usage for the reset date).
- Buy an add-on pack — top-ups are immediate.
- Upgrade your plan for a permanently higher monthly cap.
In-flight bulk jobs will continue to completion; we don’t cancel a running job when you cross zero.
”This job needs more transformations than you have available”
A bulk job’s precheck rejected the start because finishing it would exceed your quota plus add-ons.
What to do: Reduce the job’s scope (pick fewer products), buy add-on packs, upgrade, or wait for next cycle. The exact numbers are shown in the error: “needs 247, has 80 + 0 add-ons available."
"Auto-style stopped — quota threshold reached”
You’ve used 80% of your monthly transformations. Auto-styling on new product create has stopped to preserve headroom for manual work. This is the intentional 80% soft cap.
What to do: Auto-styling will resume automatically at the next cycle reset. If you need to override the threshold (rare), adjust it in Settings → Auto-style.
Bulk job errors
”Only one active job allowed — your second job has been queued”
You started a new bulk job while one was already running. The second is queued and will start when the first finishes.
What to do: Nothing if that’s what you wanted. To cancel the queued job, open the job from Bulk jobs and click Cancel queued job.
You can change the queue depth (1–5) in Settings if you need more flexibility.
”Job paused unexpectedly”
A job paused itself, usually because of a downstream issue (provider rate limit hit, intermittent network issue, your store hit Shopify’s API rate limit).
What to do: Open the job and look at the Recent events section for the underlying cause. Often you can just click Resume and the job continues from where it stopped — no duplicate work, no lost progress.
If it keeps re-pausing, that’s worth a support ticket.
”Job failed — Shopify rejected one or more product updates”
LingoVae generated the drafts successfully but Shopify rejected the metafield write for some products. The most common causes:
- The product was deleted or made inactive in Shopify after the job started.
- The product is in a state that prohibits writes (some draft/archived states).
- Your store hit a Shopify API rate limit during the job’s apply phase.
What to do: Open the job summary and check the Failed items list. Each failed item has a reason. You can usually retry the failed items only (no need to re-do the successful ones) via the Retry failed button.
Style errors
”Style is locked — a bulk job is using it”
You tried to edit a style that’s locked by a running bulk job.
What to do: Three options:
- Wait for the job to finish. The lock releases automatically.
- Cancel the job if you don’t need it. The lock releases immediately.
- Duplicate the style and edit the duplicate. Click Duplicate on the style page; you get an editable independent copy.
”Library is full — pick a style to replace”
You tried to install a catalog style, but your library is already at the cap (10 on most plans).
What to do: Replace an existing style — the modal will guide you. The replaced one moves to archived, not deleted, and any products already styled with it stay published.
”This style requires Grow” or “…requires Pro”
You tried to install a premium catalog style, or use a feature, that your current plan doesn’t include.
What to do: Upgrade. Or use a different style — the catalog has plenty of options at every tier.
Draft and review errors
”Draft is stale — the original product description has changed”
Someone (you, a teammate, an integration) edited the underlying Shopify product description after the draft was generated. The draft no longer reflects the current original.
What to do: Choose one:
- Regenerate — fresh draft from the current original. Costs one transformation.
- Apply anyway — publish the stale draft. The styled version won’t reflect your recent edits to the original.
- Skip — leave the draft for now; come back to it later.
”Could not publish — Shopify rejected the metafield write”
The apply step failed because Shopify wouldn’t accept the metafield update. Usually one of:
- The product was deleted between draft generation and apply.
- A field value exceeds Shopify’s character limit (rare — the AI tries to stay within limits).
- Your store hit a Shopify API rate limit.
What to do: Check the error detail. If it’s a rate limit, wait 60 seconds and retry. If it’s a length issue, edit the draft to shorten the offending field. If it’s a deletion, the draft can’t be applied — reject it.
Schedule and campaign errors
”Schedule overlaps with an existing schedule”
You’re creating a schedule that targets products already covered by another schedule during the same time window.
What to do: LingoVae warns you and shows the conflict. The most recently created schedule wins if you proceed. To get explicit ordering instead, use campaigns.
”Campaign publish rejected — Shopify could not write all rules”
The atomic publish of your campaign rules failed at the Shopify metafield write step.
What to do: Usually a transient API issue. Click Republish to retry. If it fails repeatedly, contact support.
”Schedule didn’t run when expected”
A schedule’s start time passed but no drafts were generated.
Possible causes:
- Your plan was downgraded between schedule creation and run time, and the new plan doesn’t include schedules. Result: the schedule is paused.
- Your store hit its transformation quota. Result: the schedule was skipped for this cycle.
- Your subscription is in a paused or pending-payment state.
What to do: Check Settings → Billing for plan/subscription status, and Settings → Usage for quota. The activity feed will also show a “Schedule skipped” event with the reason.
Storefront errors
”My storefront still shows the old description after I published”
Possible causes:
- Shopify edge caching. Shopify’s CDN caches product pages aggressively. Wait a few minutes, or force a refresh in your browser (Ctrl+Shift+R / Cmd+Shift+R).
- Theme app extension disabled. Some themes or installs may disable the LingoVae block. Check Theme → Customize → App embeds and ensure the LingoVae block is enabled.
- Entitlement metafield is stale. This refreshes every ~24 hours; force a refresh from Settings → Integrations → Refresh storefront entitlements.
”My storefront reverted to original on its own”
This is the expected behavior in several situations:
- You manually clicked Revert to original.
- Your subscription paused or downgraded, taking the product over the new plan’s cap.
- A schedule ended.
- The entitlement metafield expired and your subscription is in a paused or unpaid state.
Check the activity feed for the exact event that caused the revert.
Billing errors
”Payment failed”
Shopify couldn’t charge your card. LingoVae shows a banner and Shopify’s dunning process kicks in over a few days. The app stays functional during this period.
What to do: Update your payment method in Shopify Settings → Billing. Once Shopify successfully charges, the banner clears.
”I downgraded but I’m still being charged the higher price”
Downgrades take effect at the end of your current billing cycle, not immediately. You’ll be charged the old (higher) rate for the cycle you’re in, then the new (lower) rate from the renewal date onward.
If you want the lower price sooner, you can’t — Shopify doesn’t refund mid-cycle for plan downgrades. But your upgrades do take effect immediately with prorated billing.
”I switched plans but my features didn’t update”
Upgrades should be instant. If they’re not visible within a minute, refresh the page. If they’re still not visible, log out and back into Shopify admin.
If you’re still stuck, contact support with the timestamp and old/new plan; we can check the webhook trace.
General
”I think I found a bug”
Settings → About → Submit feature request or bug, or open the in-app support widget. Include:
- A description of what you expected vs. what happened.
- Steps to reproduce, if you can.
- A screenshot if relevant.
We respond per your plan’s SLA (see Support).
”The app is slow”
Things to check:
- Browser console for errors (often a content blocker or extension is interfering).
- Shopify admin in general — if the rest of Shopify admin is slow, it’s not us.
- Time of day — peak hours can slow AI generation. Off-hours is faster.
If the slowness is persistent and specific to LingoVae, contact support with a timestamp. We can pull traces.
”Something happened that isn’t in this list”
Open the in-app support widget. Include the timestamp and any error text you saw. We can usually find the exact event in our traces and tell you what happened.