Skip to main content
Known Participant
February 4, 2026
Open for Voting

260 credits retirés pour une photo à 40 credits .. c'est un bug ou un vol organisé ?

  • February 4, 2026
  • 1 reply
  • 13 views

la meilleure fonctionnalité serait de ne pas perdre de credits, comme si de rien n’etait .. 

 

    1 reply

    Hajar Toutsi
    Community Manager
    Community Manager
    February 4, 2026

    Hi cinemascene,
     

    Thanks for reaching out about this.
     

    We looked into the credit usage on our end to understand why it seemed like that single generation deducted 260 credits instead of 40. Here’s what we found:

    When your balance was actually at 1930/4000, you had already run several generations. By the time you were about to create the one shown in your screenshot, the balance hadn’t finished updating, it froze at 1930/4000 instead of reflecting the correct amount, which should have been 1710/4000. You can see this because the balance was greyed out and still loading.
     

     

    So the generation didn’t deduct 260 credits, it only used the usual 40. The issue was simply a delay in the credit calculation updating on the interface.
     

    One of the best ways to keep an eye on your usage is by checking Generation History under Your Stuff. It gives you a clear breakdown of every generation and the credits used.
     

    I hope this clears things up.


    Hajar