Errors during Execution: Unterschied zwischen den Versionen
Zur Navigation springen
Zur Suche springen
Cg (Diskussion | Beiträge) (Die Seite wurde neu angelegt: „During execution, errors might be generated from various places. Common errors and how to deal with them is documented here. == Execution Errors == === "tele…“) |
Cg (Diskussion | Beiträge) (Weiterleitung nach Common Errors erstellt) Markierung: Neue Weiterleitung |
||
| (60 dazwischenliegende Versionen desselben Benutzers werden nicht angezeigt) | |||
| 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. |
|||
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, |
|||
* or add an exception output pin to the step, to divert the control flow as required. |
|||
Aktuelle Version vom 23. Februar 2022, 00:56 Uhr
Weiterleitung nach:
