Error requests spend credits

[romakrivenko]

Every time you generate something and receive the error message 'We encountered an issue with your results. Please view our guidelines and try again, or if you think this was an error, provide feedback,' it consumes 1 credit, yet you receive no results.

[Kevin Stohlmeyer]

@romakrivenko you arent being charged for credits until Jan 1 2024. See the disclaimers on these pages:

https://helpx.adobe.com/firefly/using/generative-credits.html

https://helpx.adobe.com/firefly/using/generative-credits-faq.html

That being said I've read articles stating that you only are charged a credit when you receive an image - not when you get a violation. Can you confirm you are seeing deductions for the single violation?

The reason you are getting a violation on your image BTW is its 16-bit, not 8-bit.

[Stephen Marsh]

The reason you are getting a violation on your image BTW is its 16-bit, not 8-bit.

By @Kevin Stohlmeyer

Kevin, if the limitation is 8 bpc, then should a feature request (or bug report) be started for Photoshop to check for this requirement before any AI processing is even performed? This is so easily avoided from a programming perspective, it should be a non-issue.

[Kevin Stohlmeyer]

@Stephen Marsh have at it.

[romakrivenko]

Hello, Kevin. Thank you for your response.

As for the first question, I can confirm that I am being charged for credits.

Concerning your second question about whether I can confirm the charge for a single violation: Yesterday, I discovered that I've been charged for generations when I checked my current credit balance, which was 983. Since we were discussing in a group chat what can be considered as a single request, I tried to generate and check. The generation failed, but I was charged and my balance changed to 982.

After receiving your message, I spent around 20 credits attempting to replicate this bug. I managed to capture 3 or 4 unintentional and one intentional violation (when I wrote something that obviously violated the policy into the prompt). In neither case was I charged. The image was the same, and yes, it was 16-bit.

So I can't confirm the charge, as I couldn't reproduce the bug currently, but I'll be checking the balance during the next few generations to see if I can identify the conditions that led to the accidental charge.

[Trevor.Dennis]

@romakrivenko you arent being charged for credits until Jan 1 2024. See the disclaimers on these pages:

By @Kevin Stohlmeyer

Ah Hah!   I think I need to fess up that despite pointing people at the Gen Creds page dozens of times now, I have not actually read the whole thing myself.  😞