Guide

Know when to ask for help

If a fix keeps failing, check the basics and send Support enough context to investigate without another paid attempt.

Max McIsted avatar

Max McIsted

18 November 2026

A SOREN+KOLL Iris Root Face Cream jar with a white tulip on a pale stone surface.

Know when another attempt will not help

When the same correction has failed twice without progress, pausing the job can be more useful than paying for another attempt. It gives you a chance to keep the brief, source images and visible result together while the issue is still easy to explain.

This guide covers the simple checks to make first, then shows what to include in a Support report. Describing what you expected, what happened and which corrections you’ve already tried gives the team something concrete to investigate without asking you to keep reproducing the same problem.

A clear report of the problem, with the original request and result available for Support to investigate.

Before you start

  • Have the task or conversation link and approximate time ready, including your timezone. Note the status you can see so the team can connect the report with the right attempt.
  • Keep the original inputs, exact request and result or error that shows the problem together. Remove sensitive details from anything you share while leaving enough context to explain what went wrong.

Step by step in the app

Before raising the issue, check the selected brand and clear any relevant Assets filters. Return to the original conversation and keep the best existing result. Record what you expected, what happened instead and when it happened.

Open your profile and choose Support. Include the conversation link and a screenshot that shows the problem, without exposing unnecessary private information. Mention the corrections you’ve already tried so they don’t need to be repeated. You can ask SuperAgent to help summarise the issue, but you still need to review and send that information through Support yourself.

Pause repeated attempts

If you’ve asked for the same correction twice and the result still hasn’t improved, pause that job and keep the strongest existing image alongside the failed attempts. Another paid run may reproduce the fault without helping you understand it. Saving what you already have gives Support a specific request and result to investigate, while letting you move on to other work instead of continuing to change the prompt without a clear reason.

Check the brand and filters

Before reporting a missing or unexpected result, confirm that you’re in the right brand and open Assets to see whether a filter is hiding the work. These simple checks can explain why a result isn’t where you expected to find it. If the problem remains, keep the current result or error available for the report, rather than generating more versions that make the original issue harder to trace.

Return to the original chat

Go back to the conversation where you made the original request, so the brief, references and result are together. Identify the output that shows the problem and note which corrections you’ve already tried. This gives Support the surrounding context without making you reconstruct the job in a new chat, and makes it easier to explain how the result differs from the thing you asked Riverflow to make.

Collect the useful details

Collect the conversation link, approximate time and timezone, then write what you expected and what happened instead. Include the corrections you’ve already tried, along with a screenshot or visible error that shows the issue clearly. Remove unnecessary private information before sharing it. A description of what you can actually see gives Support a stronger starting point than a guess about the technical cause, particularly when the fault is difficult to reproduce.

Contact Support

Open the menu under your profile, choose Support and send the report with the relevant link. Leave this job paused while you wait for a reply and carry on with other work where you can. If that route is unavailable, keep the report and contact your usual Riverflow account contact, then save the eventual outcome with the original task so your team can see what was resolved and which version to use.

The Support option highlighted in the Riverflow profile menu.

A useful detail

If a clear instruction keeps being missed, it may need investigation as a product fault. You don’t need to keep making paid attempts to produce more examples of the same problem.

Review the work

  • Explain what you expected and what happened instead, using the visible difference to describe the issue without guessing at its technical cause.
  • Include the task link and a screenshot that shows the relevant part of the problem, with unnecessary private information removed.
  • Keep the original inputs and failed result together with the attempted corrections, so Support can follow the request and see what has already been tried.

If it needs work

If you can’t reach Support through the profile menu, retain the report and contact your usual Riverflow account contact. Include what is blocking the work and avoid guessing at the cause or repeatedly paying to reproduce the same fault.

Build on the result

Keep the report in the original chat or alongside the task link. Add the outcome when the issue is resolved so your team knows which file or workflow to use next.