Skip to main content
O
Opprince
Participant
July 15, 2026
Answered

Kling 3.0 Omni failing since last night ("Something went wrong") — free trial expires in 6 days

  • July 15, 2026
  • 5 replies
  • 90 views

Hi,
I'm on a free trial of Adobe Firefly and have been using the Kling 3.0 Omni model to generate video for an ongoing project. It was working normally yesterday until the evening, when every generation attempt started failing with:
"Something went wrong. Please try again later."
Details:
Model affected: Kling 3.0 Omni (video generation)
Standard Firefly model: not tested since, but based on other reports this may still work normally
Started: yesterday evening, no changes made on my end (same browser, same account, same type of prompts/reference images I'd been using successfully all day)
Tried: refreshing, logging out and back in, closing and relaunching the browser
Credits: I still have generative credits available and an active subscription plan
This appears to match other reports on the Adobe community forums of partner models failing with this same generic error over the past several weeks.
I've attached a HAR file capturing the error as requested in your generation-error logging guide.
Given that this is a platform-side issue and not something I can resolve on my end, I'd like to request a trial extension for the days I've lost to this outage — my free trial is due to expire in 6 days, and I haven't been able to use the feature I signed up to test because of this bug.
Please let me know if you need anything else from me (prompt text, reference images, timestamps of failed attempts, etc.)
Thanks,
[Promise]

    Correct answer Hajar Toutsi

    Hi Opprince,
    Thanks for the detailed breakdown, it was helpful.
     

    I looked into your account activity, and here's what I found: the failures weren't tied to a platform-wide block or outage on our end. What's actually happening is that the generations are being rejected because the prompt text is going over our current length limit. That's why the error shows up as a generic message rather than something more specific, it's on our list to make that error clearer so it's obvious what's going on.
     

    A couple of things that would help going forward:

    1. Could you confirm you were specifically selecting the Omni variant, rather than one of the other Kling options? Just want to make sure we're troubleshooting the right one.
    2. Try trimming your prompt to under 2,500 characters and running it again that should resolve the immediate error.


    On the "stuck on Creating" generation that later refunded, that one looks like it may have hit a separate, brief instability window we saw affecting video generations more broadly, so the auto-refund there was working as intended.

     

    Since this turned out to be a prompt-length issue rather than downtime, I'm not able to process a trial extension on that basis. That said, if you run into the error again after shortening the prompt, send over the exact timestamp (or a screenshot showing it) and I'll trace that specific attempt to see what's going on.

    Appreciate your patience while we investigated this.

     

    Hajar

    5 replies

    Hajar Toutsi
    Community Manager
    Hajar ToutsiCommunity ManagerCorrect answer
    Community Manager
    July 16, 2026

    Hi Opprince,
    Thanks for the detailed breakdown, it was helpful.
     

    I looked into your account activity, and here's what I found: the failures weren't tied to a platform-wide block or outage on our end. What's actually happening is that the generations are being rejected because the prompt text is going over our current length limit. That's why the error shows up as a generic message rather than something more specific, it's on our list to make that error clearer so it's obvious what's going on.
     

    A couple of things that would help going forward:

    1. Could you confirm you were specifically selecting the Omni variant, rather than one of the other Kling options? Just want to make sure we're troubleshooting the right one.
    2. Try trimming your prompt to under 2,500 characters and running it again that should resolve the immediate error.


    On the "stuck on Creating" generation that later refunded, that one looks like it may have hit a separate, brief instability window we saw affecting video generations more broadly, so the auto-refund there was working as intended.

     

    Since this turned out to be a prompt-length issue rather than downtime, I'm not able to process a trial extension on that basis. That said, if you run into the error again after shortening the prompt, send over the exact timestamp (or a screenshot showing it) and I'll trace that specific attempt to see what's going on.

    Appreciate your patience while we investigated this.

     

    Hajar

    O
    OpprinceAuthor
    Participant
    July 16, 2026

    Hi Adobe team,

     

    I can confirm that Kling 3.0 Omni is working for me now. The issue was caused by my prompts exceeding the current character limit. After shortening the prompts to below 2,500 characters, video generation started working normally again.

     

    The “Something went wrong” message did not clearly explain that the prompt was too long, so a specific prompt-length warning would be helpful for other users experiencing the same problem.

     

    Thank you to the Adobe Community team for reviewing my attempts and explaining the limit. My original issue is now resolved.

      O
      OpprinceAuthor
      Participant
      July 15, 2026

      Hi Hajar,

      Thanks for the reply, but I don't think this is a generation-limit issue — let me clarify:

      I successfully used Kling 3.0 Omni multiple times earlier in my trial, including as recently as yesterday evening. It stopped working mid-session, not at the start — there was no point where I "ran out" and then got blocked; it was working normally and then began failing with a generic error on every attempt.

      I checked my account menu and I still have Premium generations remaining, so this isn't a quota exhaustion issue. To be specific about what's actually happening:

      1. Generations fail immediately with: "An error occurred. Please try again later."
      2. On one attempt, it instead got stuck indefinitely on "Creating" for 5+ minutes with no progress, and after refreshing the page, that generation's credit was refunded automatically.
      3. After the refund, trying again returned to the same "error occurred" failure as before.

      This matches what other users have reported in this same board over the past several weeks — Kling and other partner models failing with this identical generic error while the standard Firefly model continues to work normally. It looks like a backend issue with the partner-model integration itself, not something tied to my account's generation count.

      Given that a real portion of my 7-day trial has been spent unable to use the feature I signed up specifically to test, could you look into extending the trial period to account for that downtime, rather than the quota explanation? Happy to send a HAR file or screenshots of the specific error if that helps investigate.

      Thanks, [Promise]

      O
      OpprinceAuthor
      Participant
      July 15, 2026

      Update on this — same issue, new twist:

      I let a Kling 3.0 Omni generation sit for over 5 minutes stuck on "Creating" with no progress. Eventually refreshed the page, and the credit for that job was refunded back to my account (so at least that part self-corrected). But now that I've tried generating again, it's back to the original "An error occurred. Please try again later." error from before.

      So the pattern for me has been: working normally → stuck indefinitely on "Creating" → refresh → credit returned → back to instant failure on retry. Still isolated to the Kling partner model; haven't tested standard Firefly again in the meantime.

      Posting this in case the "stuck on Creating" state is a related symptom of the same backend issue rather than a separate bug — seems relevant for whoever's investigating this.

      Hajar Toutsi
      Community Manager
      Hajar ToutsiCommunity Manager
      Community Manager
      July 15, 2026

      ​Hi Opprince,
      Thanks for taking the time to write in.

      When you purchased the plan, a 7‑day trial period was activated. During this trial, you have a limited number of generations available for both Standard and Premium features. You can check this from your account menu in the top right corner of the Firefly page.

       

      ​

      Account menu icon​​​​​
       

      If you have already consumed the amount of generations available for Premium features, then you won’t be able to use Kling 3.0 Omni since it’s a Premium model. 

      If you’re satisfied with your experience, you simply need to wait until the 7‑day trial ends. At that point, the credits you purchased will be added to your account automatically, and you can start using credits to generate with Premium models such as Kling 3.0 Omni.

      Please let us know if you have never been able to use Premium features during your trial period, we’ll be glad to assist further.

      Hajar

       

      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices