Errors during Execution: Unterschied zwischen den Versionen

Aktuelle Version vom 23. Februar 2022, 00:56 Uhr

Weiterleitung nach:

@@ Zeile 1: / Zeile 1: @@
+#redirect [[Common Errors]]
-During execution, errors might be generated from various places.
-Common errors and how to deal with them is documented here.
-== Execution Errors ==
-=== "telegram-data for non-triggering pin "x" of inactive step "Y" ===
-A ''telegram input'' pin (also called "''mailbox pin''") received a value '''after''' the step has already finished its execution. This is reported for non-triggering pins only - if it was triggering, a new activity would have been started. However, as the pin is non-triggering, the value is lost and there is noone to handle it.
-<!-- This error is reported to the containing compound action. Because both the sending and the receiving steps have already finished (with or without success), the error cannot be reported at their exception output pins.
--->
-Fix:
-* check if a mailbox pin is really required
-* either make sure that the input pin receives its value earlier (i.e. while the step is still being executed),
-* or set the "ignore exception" behavior of the target step,
-* or add an exception output pin to the target step, to divert the control flow as required. Notice, that this creates a strange situation, in that both any trigger-output AND its exception output pins may get a trigger value However, the exception would be "magically" written later, without the step being actually active. Also, this exception output might trigger multiple times.