13.5 Possible errors in scenarios
(12) Node error scenario is not active

Cause: running a Prod version of a scenario that uses a Nodul type scenario (customized node) in the Pause status.
Solution: switch the Nodul type scenario from Pause (1) to Active status, e.g. using the Enable button (2).

Start node not found Error code: latenode.runner.start_node_not_found

Reason: absence of a node in the scenario that would perform the function of a trigger, i.e. trigger the scenario.
Solution: add one of the trigger nodes to the scenario.
