Elanorya

Jewelry AI

Reporting a result opens a review, not a refund

The app answers two kinds of disappointment in two unrelated ways. If the job failed, the credit for that job is returned and nothing is retried on your behalf. If the job finished and handed you an image you cannot use, the report path is a content review, and the sheet you send it from says so before you send it.

One feeling, two systems

There are two ways a run can leave you without a picture you can use, and the app answers them from opposite directions. In the first, the job did not finish: nothing was delivered. In the second, the job finished exactly as far as the system is concerned, and what came back is wrong for your piece.

Only the first of those is a delivery problem. It is settled by the credit system without any action from you: the credit for that job comes back. The job is also not attempted again on your behalf, so a failure ends quietly rather than turning into a queue of retries.

The second is not a delivery problem at all. The image was produced and handed over, and your objection is to what is in it. That objection has its own path, and that path is a review of content rather than an adjustment to your balance.

What a report does after you send it

The steps below describe the reporting path only. A failed job never enters it.

  1. You open the report sheet from a finished result

    The entry point is the result itself, which means the picture already exists. That is the signal that you are on the content side of the boundary rather than the delivery side.

  2. You choose the reason that matches what is wrong

    The reasons are offered as separate choices rather than one open complaint field. The first of them is that the product changed, which is the objection a jewelry seller brings to a finished image most directly.

  3. The report is entered as a content review

    What you have started is a review of the image and the reason attached to it. The sheet states this in its own words: "A report starts a content review; it does not automatically refund money or credits."

  4. Your credit position is unaffected by the report itself

    Sending a report is not an event in the credit system. The same sentence closes with the reason: "Failed delivery is handled separately by the credit system." That separation is what makes the report safe to send and useless as a billing step.

What each side of the boundary actually returns

Neither remedy returns a replacement image. What they return is different from each other, and neither is what the other is often expected to give.

A failed job returns the credit for that job.
It returns nothing else: no image, no retry, no queue position. The next attempt is a run you start.
A report returns a review of the content.
The sheet is explicit that it does not automatically refund money or credits, and it says so before you send rather than afterwards.
The two are answered by different parts of the product.
The sheet points at the credit system for failed delivery, which is also why sending a report about a failure adds nothing to what already happened.

Before you send a report

  • Confirm an image was actually delivered — if the job failed, the credit side has already acted.
  • Read what is wrong in terms of the piece: what changed, and where in the image it changed.
  • Pick the reason that describes the image in front of you rather than the outcome you want.
  • Plan the listing as though your balance will not move, because the sheet says it will not.
  • Decide separately whether the piece is worth running again; that decision is yours either way.

What this page does not cover

  • Credit amounts, prices, or what a run costs — no figure appears on this page.
  • Refund policy, store refunds, or any money-back process; a report is not a step in any of them.
  • The moment your credit is deducted and what the app tells you just before it, which belongs to the page about when your credit is spent.
  • Why a generation is blocked before it starts, and what to do about each blocked state.
  • What any individual review concludes, or how long it takes.

Questions

If a result comes back wrong, do I get the credit back?

Not through the report. The report sheet states it directly: a report starts a content review; it does not automatically refund money or credits. Credit comes back when delivery failed, and that is handled by the credit system rather than by anything you send.

Do I need to report a job that failed?

No. Failed delivery is handled separately by the credit system, and the credit for that job is returned without a report. There is nothing for the review path to look at, because no image was produced.

Does the app try a failed job again on its own?

No. There is no automatic retry. The credit for the failed job comes back and the job ends there; if you want the piece again, you start a new run yourself.

Is reporting the right step when the generation never started?

No. Reporting a result is a different flow from a run that never started. A run that is blocked before it begins has its own set of causes and its own page; the report path only applies to a result that exists.