Bug with ID in Flash with Tasker Layout - existing flash with same ID in another Task is not replaced

[francwalter]

Hallo

I appreciate very much the Tasker Layout in Flash Actions and I always use it!

The new feature ID is useful, I use it more and more.

But I noticed a bug (or at least a misinterpretation of the inline help) of the ID field.
I read there (inline help):
"ID
If you set an ID and and existing flash is already showing with the same ID, it'll be replaced by the new one.
..."

This works only in the context of one Task, but not with the same Flash-ID of another Task.

I have some Tasks where I need to call a new Task (e.g. to stop and clean etc. the main Task). Here (in some child Task) the new Flash does NOT replace the Flash of the parent Task with same Flash-ID.

A workaround could be to use parameters in the Task or a Return Action, but it would be easier to use the Flash-ID globally.

Or maybe it is not ment like this and the help is not exact.

Thanks.

Frank

Android 9.0 with Tasker 6.2.12-rc

[João Dias]

Hi! Can you please export a minimal example of that as an URI (not a link, but a direct URI) and paste it here so I can then import it and test it myself?

Thanks in advance!

Thank you for your contact.

   Join: connect multiple devices (send pushes, remote SMS, notifications) on Android, Windows, Mac, Linux

   Tasker: customize/automate anything on your phone!

   AutoApps: add advanced functionality to Tasker via plugins

     

João Dias

[francwalter]

joaomgcd schrieb am Mittwoch, 11. Oktober 2023 um 14:52:41 UTC+2:

Hi! Can you please export a minimal example of that as an URI (not a link, but a direct URI) and paste it here so I can then import it and test it myself?

I was not able to reproduce it in a minimal example, so I copied my Tasks with the issue and started to deactivate more and more Actions till I found the culprit!

In my Task there was a Flash Action in the beginning, quite useless though, saying that my Task starts. With a timeout of 1 sec only and with Continue Task Immediately: yes.

It had also the ID: 1 as all my other Flash Actions. 

When I disable this Flash Action or if I delete the ID (or set it to another value than 1) or if I set  Continue Task Immediately: no or if I set the Timeout to more than only 1 sec - than that later Flash Action with ID:1 which was not disappearing, suddenly disappears as expected, when the Flash Action with ID:1 of the other Task runs.

So somehow if there are two Flash Actions with the same ID and both set to Continue Task Immediately: yes and the first one has a short Timeout (1sec or less) then the second one could be not reached by ID.

But I cannot reproduce it with a simple Task, so I think it happens also because my Task is too long (contains some Wait in Loop Actions) and somehow the ID of the second Flash Action is mixed up with the first one.

This might be a bug, I guess. Maybe it is simpler than that, but I didnt find it and give up now.

Now that I know how it happens, it is no issue to me anymore, thanks :)
frank