Skip to content

Common Problems and Solutions

Working in Craftology is a creative and iterative process, and like any creative tool, things don’t always behave exactly as expected. Most issues are not bugs, but rather small mismatches between what the system understands and what the user intends. This guide explains the most common situations users encounter and how to resolve them.

When the model ignores your references

One of the most frequent frustrations is when the generated result does not match the references you provided. For example, you may expect a male character but receive a female one, or a human turns into something stylized or unexpected.

In most cases, this happens because the prompt and the references are not aligned. The model tends to rely more heavily on the text description than on the images. So if your prompt describes one thing and your references show another, the model will follow the prompt.

The best way to fix this is to go back and carefully review how the asset is described — both in the prompt and in StoryCraft. Make sure everything is consistent. If you are using multiple references, it helps to explicitly tell the model how to use them, such as assigning one reference to lighting and another to composition.

When changes don’t appear after generation

Sometimes the agent reports that it has created or updated characters, environments, or shots, but nothing appears on your screen. This can feel like something is broken, but usually it’s just a simple interface issue.

In these situations, the most effective solution is to refresh the page. The data is often already there — it just hasn’t been displayed yet.

When generation fails with an error

At some point, you will likely encounter a generation error. It might look intimidating at first, especially if the message is long or technical.

However, the important detail is that most errors already include instructions on how to fix them. Sometimes the prompt needs to be rephrased because it violates model rules. Other times the system is simply busy, and waiting a bit before retrying solves the problem.

Instead of skipping past the message, take a moment to read it carefully — it often tells you exactly what to do.

When the agent seems stuck or unresponsive

There are moments when the agent appears to freeze, stops responding, or doesn’t accept new input. This can be confusing, especially if you’re not sure whether something is wrong.

In many cases, the agent is actually still working — especially during larger tasks like generating multiple assets. When this happens, the interface may temporarily block input.

You can open the reflection block in the agent’s message to see what it is currently doing. If the system allows you to type, try asking a simple question like “What is the status of the current operation?” — this often helps resume interaction.

When results don’t match your expectations

Sometimes the system produces results that feel off — wrong style, incorrect mood, or unexpected composition. This usually comes down to missing or unclear context.

Craftology works best when it has a clear understanding of your intent. If the prompt is vague, the model fills in the gaps on its own, which may not align with your vision.

Improving this is less about fixing errors and more about providing better guidance. Take time to define the concept clearly — style, tone, environment, and key elements. A small improvement in clarity at the start can save many iterations later.

When you find yourself regenerating too many times

It’s normal to iterate, but if you find yourself constantly regenerating without getting closer to the desired result, it usually means the process is not structured.

Instead of repeatedly clicking generate, pause and evaluate what specifically needs to change. Adjust only the relevant part of the prompt or references, and keep stable elements unchanged.

Over time, this approach reduces both effort and cost, because each iteration becomes more meaningful instead of repetitive.

When references don’t seem to work

Adding references does not automatically guarantee better results. If references are unclear, conflicting, or not properly described, the model may not use them effectively.

A helpful technique is to explicitly guide the model. For example, instead of simply attaching images, describe how each one should be used. Referring to them in order — “reference 1,” “reference 2,” and so on — can also improve consistency.

When the interface behaves unexpectedly

Occasionally, buttons may not respond or elements may not update as expected. This is usually not a deeper system issue.

A simple page refresh often resolves these problems immediately. It’s a small step, but one that saves time before assuming something more serious is wrong.

When you’re doing too much manually

Craftology is designed to automate much of the creative workflow, but sometimes users fall into the habit of manually editing everything — adjusting each shot, rewriting every detail, or recreating assets from scratch.

This approach quickly becomes inefficient. Instead, it’s better to work at a higher level: update the project description, refine StoryCraft, or guide the agent with clearer instructions. The system is built to propagate those changes across the project.

When operations take longer than expected

Some tasks, especially large ones, can take time. If you’re generating many assets or working with complex scenes, delays are normal.

The key is to distinguish between “slow” and “stuck.” If you see activity in the reflection block, the system is still working. If there’s no activity at all, then it may require intervention.

If you haven't yet discovered a solution to your issue

Do one of the following: