Editing a running tunnel

UA	US	RU

UA	US	RU

The practice of "spontaneous editing" of tunnels is not the best idea, since it prevents a fully objective assessment of the effectiveness of the tunnel. The tunnel editor may try to hide his mistake when creating the tunnel, but the changes are still saved in the database.

The subscriber is sent the content that is in the block at the time it is sent.

Examples:

There is Block 1. Behind it is Block 2 with a sending delay of 10 minutes. The subscriber receives Block 1 and waits for Block 2 to be sent. If at this moment the contents of Block 2 are changed, the subscriber will receive not the original message that was in Block 2 at the time of subscription, but the message that will be in Block 2 at the time it is sent.

2. In the tunnel there is a block with a button from which a direct connection is extended to Block 2, and content A. The subscriber subscribes to the tunnel, but does not click on the button from Block 1. The author of the tunnel changes the content of Block 2 - now it is B. If the subscriber is now clicks on the button, thereby fulfilling the condition for sending the second block, he will receive B - the edited contents of the second block.

3. The block contains a message with a button like message template. In the interval between the subscriber receiving the message from the block and clicking on the button from the message, the template was edited. Now it contains not message A, but message B. When the user clicks on the button, he will receive not the original message A, but the edited message B. If we now edit the template again and replace B with C, then the next time the button is clicked, the subscriber will receive a message B.

What happens if you edit the structure of a running tunnel?

The tunnel block sending queue is formed immediately after the previous block is sent.

If you delete a block following a block that has already been sent to a subscriber, then such a block will not arrive. All subsequent blocks will not arrive either. For the subscriber, the tunnel will be considered completed.

If you need to send certain tunnel blocks even for subscribers for whom it has already ended, then to do this you need to hover your mouse over the tunnel block we need and a context menu will open in the upper right corner, in which we need to select the “Send from previous block” button.

After which we have a menu with two items, we are interested in “Send to everyone in the previous step”. It displays the exact number of all users in the previous step (in this case 1). If you click on this button, then all the conditions for sending this tunnel block will work for subscribers of this tunnel, including those for whom it has already ended earlier.