Fix a workflow that does not start in Kotia: readiness check
Find why a workflow will not start from the message on the card: an unselected field, a missing source, document, or access. Checks and fixes for each case.
On this page7
If Kotia does not start a workflow, the message on the card will tell you what is preventing you from starting. The cause may be an unselected translation language, a missing document, or an incorrect connection. The check runs before any paid steps and helps you find and fix a specific setting.
First, read the cause on the flagged card. Common problems are shown at "Start." Fix the named field or connection, then check the other notes. Common causes are covered below: problems with sources, recipients, memory, and an unfinished previous run.
Example: translation does not start
You connected a document to the "Translate into another language" card, but you did not select a language. Open the translation settings and specify a language. If the empty-input message remains, check the source document itself. Its title does not replace its content.
Fill the document with text or choose a different one. Then make sure the path from "Start" leads through the source to the translation. As a result, the step gets both required conditions: material to translate and a selected language.
How to find and fix the cause
- Look at the messages on the cards and next to "Start". Before a run, they are marked as warnings. After a failed attempt, they are marked as errors.
- If a message refers to a collapsed group, expand it. The group shows that there is a problem inside, and the details are on the specific step.
- Zoom in on the area so you can read the text. Open the card's settings or check its incoming connections.
- Fix the named field, source, or connection. If the issue is with a document, open it and check the content.
- Review the other warnings. Changing one field does not fix errors on other steps.
- Run the workflow again after fixing the causes. If the run started but stopped at one of the cards, use the guide to execution errors.
If the check does not allow the run to start, paid steps are not performed. Charges for previous runs do not change as a result.
Check the start of the chain and the connections
| Situation | How to fix |
|---|---|
| Nothing is connected to "Start" | Connect the start to the first working step or data source |
| A source passes data on, but is not connected to "Start" itself | Restore the path from "Start" to this source |
| The connections form a closed loop | Remove the feedback connection. To repeat steps, use a loop |
| A card needs text, but only "Start" is connected to it | Add a document, "Data," or another source of material |
| A checking card has no input | Connect the text it should check |
"Start" only tells the workflow to begin. It does not pass along the source text. For example, an AI detector needs the material itself. Style and memory do not replace a text input either, if the card requires one separately.
Check fields, documents, and recipients
The required fields in the settings must be filled in: the task or order, if they are needed, the translation language, the selected folder, and the site or sending channel. For some services, a field can be replaced with incoming data. The card's own instructions say so.
The selected document, folder, or recipient must remain accessible. If an item has been deleted, choose another one. Sending to WordPress requires a WordPress site, and sending to Telegram requires a channel on that platform.
Check empty input documents separately. A title such as "Product description" won't help the AI if there is no text inside. The empty-source warning appears when a step definitely will not get the material it needs. An empty document next to another, non-empty source does not always interfere with the work by itself.
Not every result is plain text. For example, an article outline or a list of sources cannot be written directly into a text document the way a finished post can. If a card reports that it cannot read the result, choose a suitable next step following the service's instructions.
Check comparison, memory, and repetition
| Setting | What is required |
|---|---|
| "Compare two versions" | Two inputs: one with the role "before," the other "after" |
| Memory maintained by the agent | One step that updates this memory. Separate cards for different tasks |
| Manual memory | Several steps can use it. The agent does not rewrite it |
| Loop | Correct input and output for the section, an allowed number of repeats, and cards that the loop supports |
| Repeating section that is too large | Reduce the number of repeats or the contents of the section |
Repetition is configured on the group. A circle of connections drawn on the workflow does not create a loop, and it interferes with the run.
Check access and the previous run
If a model requires a subscription, check your subscription or choose an available model.
If this workflow is already running, wait for it to finish or stop the current run. A partial run also requires results from the preceding steps that can be reused.
Even when you run a single section, the readiness of the entire workflow is checked. A warning in another branch may also need fixing.
What a successful check does not guarantee
The check confirms that the workflow is set up to start. It does not guarantee that an external site will respond, that the service will find the materials you need, or that your balance will cover any amount of work. Input data and access can change even after the run has started.
If an error appears during execution, do not limit yourself to checking required fields. Open the problem step in Runs, read the cause, and check what finished before it.