BUG in action - Turn a Telegram message into a process

Good day. The action doesn't even start - there is no token selected in it.

[quote] [file]23762[/file] lace [file]23762[/file] OneBox production wrote: [file]23762[/file] Good afternoon. The action doesn't even start - no token is selected in it. [file]23762[/file] [/quote] [file]23762[/file] This is not an action that works. [file]23762[/file] I simply selected a new action to take a screenshot. [file]23762[/file] Here is a screenshot with the current action. [file]23762[/file] [file]23762[/file]

Okay, that's better and in theory it might work. Then you receive a new message from the client, it is added to the process but the process does not reopen? Can you give an example of a process that should reopen and a link to today's event after which this action did not occur?

[quote] lace OneBox production wrote: Okay, that's better and in theory it might work. Then you get a new message from the client, it's added to the process, but the process doesn't reopen? Can you give an example of a process that has reopened and a link to today's event, after which this action didn't occur? [/quote] https://askoart.1b.app/30281/ The process was done a couple of minutes ago. 1) Process in status close - 2025-03-24 16:51:37 2) SMS from the client - 2025-03-24 16:52:06 A message just arrived, and the SMS is visible in the process interface elements and in the telegram block. BUT the status did not switch.

BUG is current. The action does not switch the closed process stage! Will this issue be resolved?