--- title: Test an action or run a scenario manually in Link’nX description: Run a Link’nX action or scenario on demand, test a KNX action with a custom value and check the result on the equipment. canonical: https://wiki.can-nx.com/en/guides/link-run/ language: en product: Link’nX audience: - administrateur - installateur context: "Link’nX web: Actions and Scenarios lists, launch button and activation" --- # Test an action or run a scenario manually in Link’nX Context: Link’nX web: Actions and Scenarios lists, launch button and activation The play triangle in the Link’nX lists immediately runs an action or a scenario’s sequence, without waiting for its trigger. For a KNX action, you can send the configured value or test a custom value. Intended for administrators and installers authorized to work on the equipment of the Link’nX context. These commands request execution on the installation: first check the project, the gateway, the target equipment and the planned actions. Do not use them simply to make a configuration warning disappear. ## Run an action 1. In **Actions**, [find the action](https://wiki.can-nx.com/en/guides/link-lists/) and [check its configuration](https://wiki.can-nx.com/en/guides/link-action-edit/). Exit **Select** if its buttons are hidden. 2. Click its play triangle on the right, whose tooltip is **Launch action sequence**. 3. For a KNX action, choose **Test with default value** to request the configured value, or **Enter custom value** for a test with a known value suited to the equipment. 4. If you chose **Enter custom value**, the **Custom value** window opens. Fill in **Value**, then click **Ok**. **Cancel** closes this window without requesting the test. 5. Wait for **Action is running**. In the **Custom value** window, the initial value shown is 0: do not confirm it without checking that it suits the intended data type and command. For an action of a type other than KNX, the triangle directly requests execution with the configured value. In a scenario’s form, the triangle in a circle, to the right of an action card, also requests an immediate test of that single action, without waiting for its delay: see [setting a scenario’s sequence](https://wiki.can-nx.com/en/guides/link-scenario-sequence/). ## Run a scenario 1. In **Scenarios**, find the row. If necessary, view its [composition](https://wiki.can-nx.com/en/guides/link-compose-scenario/) to know the action sequence and its delays. 2. Click the **Launch action sequence** triangle on this row. This request does not present the custom value form of KNX actions. 3. Wait for **Scenario is running!**. ## Enable or disable a scenario A scenario’s switch changes its activation state. After toggling it, wait for **Updated!** and check the displayed state. Activation and the launch triangle are two separate commands. An execution already requested is not canceled by closing the page. Do not rely on a second click or on disabling the scenario to reverse commands already carried out. To establish precisely how a manual launch handles conditions, a disabled scenario or a sequence already in progress, or for a stop or resume behavior that is not established in your configuration, contact support before a test whose result could be undesirable. ## Check the result - After **Action is running** or **Scenario is running!**, check the expected observable result on each device: the message indicates that execution is requested, the device shows whether it took place. - For a scenario, view [the scenario history](https://wiki.can-nx.com/en/guides/link-history/) if useful. Take the configured delays into account before launching again. ## Troubleshooting For **The test could not be performed**, or if the expected result is not observed: 1. Check the context, the selected action and its known parameters. 2. For a scenario, check the name and time in the history. 3. Do not click the launch button repeatedly to diagnose a lack of response. If these checks have already been made, contact support@can-nx.com with the product, the gateway, the action or scenario, the time, the message and the observed result.