How to Report a Bug – and Earn Credits by Helping Out

How to Report a Bug – and Earn Credits by Helping Out

When something doesn’t work as expected, it’s more than just a glitch — it’s an opportunity to make the system better. At Cogniwerk, we rely on the sharp eyes of our users to help us detect and fix technical issues quickly. That’s why we’ve made reporting bugs as straightforward as possible — and we reward valid reports with credits.

Here’s how to use the Bug Report Form efficiently and contribute to a better experience for all.

 

1. Where Did It Happen?

The first question in the form asks you to identify where the issue occurred. This helps us locate the affected module right away. Please choose the section that best matches your situation:

• Interface – While generating an image

• Training – During the training of a custom model

• Storage – Inside your personal model or image storage

• Homepage – On cogniwerk.ai’s landing or navigation pages

• Blog – In the editorial content area

 

2. Did the Problem Persist After a Refresh?

Sometimes, browser hiccups or cache conflicts can cause temporary errors. Before reporting a bug, please try the following:

• Refresh the page and check if the issue remains.

• Clear the browser cache, or

• Open an incognito window (in Chrome: click the three dots in the top right → New Incognito Window) and try again.

This step helps us distinguish platform issues from local browser behavior.

 

 

3. What Were You Trying to Do?

In this field, describe what action you were taking — in plain terms. There’s no need to share your creative prompt or detailed settings.

✅ Example:

“I switched models from SDXL to Flux, selected a custom model, and when I clicked generate, the process failed.”

The goal is to allow our team to reproduce the error by following your steps.

 

4. What Went Wrong?

Now is the time to explain what exactly failed — or didn’t happen.

• Did the button not respond?

• Was there an error message?

• Did the system freeze or ignore your action?

✅ Example:

“After pressing ‘Generate’, the loading icon appeared but nothing happened. No image was created and no error message was shown.”

The more detail you provide, the faster we can identify the cause.

 

 

5. Upload Media (Optional, but Highly Recommended)

A screenshot or short screen recording often says more than words. If possible, attach:

• A screenshot of the error

• A screen recording of your process

• Any visible system messages or log codes

This step increases the likelihood of a fast resolution — and qualifies your submission for a credit reward.

 

6. What Makes a Good Bug Report (and What Gets You Credits)

To ensure fairness, we reward bug reports that are:

• Reproducible: We can follow your steps and replicate the issue

• Unique: The issue hasn’t already been submitted

• Complete: The report includes enough context to start debugging

Validated reports are rewarded with credits as a token of appreciation — helping both you and the community.

 

 

7. Final Thoughts: Every Report Matters

A well-written bug report does more than solve one user’s problem. It helps us build a more stable, more powerful system for everyone. And it reminds us that behind every technical issue is someone who took the time to help fix it.

Thank you for being part of that effort.