Errors and Solutions

When creating an automation, Monkedo checks your flow and configuration. Issues are split into two levels:

Open the panel via the yellow warning button on the right side of the top menu bar to review both errors and warnings.

These must be fixed before you can deploy an error-free automation.

In the editor, each component can be executed one by one using the Run button. However, to run the full flow or to save the automation and run it in the background, at least one trigger must be added.

Automation is executed with only one trigger. More than one trigger should not be added.

A component can receive data either from another component or the info panel. This setting is adjusted with the toggle on the right side of each input in the panel.

This error occurs if data is supposed to be taken from another component for an input, but no connections are made from it.

Next to each input, it is indicated whether it is mandatory. If it is mandatory, there is a red ***** sign. This error occurs if data is supposed to be taken from the info panel for a mandatory input, but the field is empty.

Under the Flow Control category, there is an End Iteration component. This component should be used with iteration components. It is used to abruptly end an iteration under certain conditions.

If the End Iteration component is not connected to an iteration component, it cannot be used.

Warnings improve reliability but do not stop a deployed automation from running.

This warning is common to several different scenarios. The automation can still be deployed and will run; however, some connected nodes may never execute. Let's address these scenarios:

In components that perform a unique query, such as Get Task, Find Note, etc., there is an output named Not Found. This output is activated when no data meeting the search criteria is found. If there is data matching the criteria, the Not Found output becomes inactive, and other outputs become active. In this case, since both the Not Found and other outputs of the component cannot be active at the same time, connecting them to any component later in the flow will generate this warning.

For example, in the above flow, the two inputs of the Set Entity Field component cannot be active at the same time.

Solution: Ensure that outputs that are not active at the same time are not connected in the flow.

There is a Condition component that allows incoming data to be evaluated based on specified query rules. Each named condition output becomes active when its rule matches; if none match, Otherwise is active.

For example, according to the condition added in the above flow, either a named condition output or Otherwise will be active — not both — so a downstream component wired to multiple condition outputs at once cannot run.

Solution: Ensure that outputs that are not active at the same time are not connected in the flow.

In iteration components (Iterate List, Iterate Table, and Repeat) there are three different outputs: the main output, number, and done. In these components, the main output and number are active in each iteration, but the done output only becomes active when the iteration ends.

For example, above, the outputs item and done, which cannot be active at the same time, are connected in the Create Task component in the flow. Therefore, the downstream component cannot run.

Solution: Ensure that outputs that are not active at the same time are not connected in the flow.

Iteration components repeatedly execute the node. Naturally, the rest of the flow does not proceed until the current iteration completes. Once the iteration ends, all data in that node is reset.

Let's look at the flow above. The Iterate List component processes all the inputs in the list. After this, the flow moves to the Iterate Table component. At this point, the first input of the "Create Task" component will be empty because the data in the Iterate List block has been reset. Consequently, even if the other inputs are ready, the downstream component cannot function because its first input is not available.

Solution: The Iterate Table component should be executed first in the flow. If it provides data that will be used in the iteration, this data should be stored using the Set Named Value component.

Data from Iteration Outside Component

Iteration components repeatedly execute the node, and when the process is completed, all data in that node is reset. Therefore, all connections within the node must be established.

For example, in the flow above, flow number 1 runs first. When we reach the Create Task component, one of its inputs needs to come from flow number 2. However, since flow number 2 has not been executed before the iteration node ends, the Create Task component cannot run.

Solution: Since all connections in the iteration node must be established, the order of the flows needs to be changed. Click on the connections having numbers to open the connection detail window. From there, change the number of flow 2 to 1.