Community
Feature request: Use a generic or assignable username for flows triggered by timer
In /admin/processes the column "User" shows
1. For manual triggered flows - the name of the user who triggered it
2. For timer triggered flows - the name of the user who last published the flow
Point 2 will make it hard to distinguish if a flow was triggered manually or by timer.
Also if you just want to filter on processes triggered by user xxx you will get a lot of false positives.
Finally - if you remove this user, maybe the person started at another company, the flow will not be triggered at all until you republish it with an existing user!!!
It wood be good if all flows triggered by timer had a generic username like "Timer" to distinguish them.
Or it could be definable in a setting like /admin/settings/user_name_to_trigger_timerbased_flows
Posted by Dennis 11 days ago
Only the first 10 items in /admin/processes has the checkbox in the field "Flow" checked
![](https://files.readme.io/516678694a7cf44c507948b63ce7c5cffbc61d515dc83fb90468cd663a8a61e8-image.png)
<br />
If I go to /admin/processes?term=workflow:<any-flow> it seems only the first 10 items in the list in the field "Flow" will have the checkbox checked.
This seems similar to the fix in 2.12.3:
fix: schedule and nextRunAt fields in admin interface when listing workflows
Maybe that fixes this field too (I did not install it yet, so I don't know) but as the fix mentions two specific fields in another view, it might not. Just so you can check it.
Posted by Dennis 11 days ago