Who would benefit? |
Expression engine users |
What impact would it make? |
User friendly and clear feedback from system |
How should it work? |
From what I can see, the "Apply on existing entities" jobs can only run one at a time - if this is incorrect please let me know. It would be good that if I went to run the same job on another field, the system would let me know that the job is already running for another field and therefore won't try and run the job |
Why is it needed? |
Additional feedback, background or context:
I also encountered this problem, job started but updated never appeared. With a ticket I was able to see one errored and one never completed. The ability to view these in the Log file would be preferred.
These jobs should appear in the Jobs list like Mass Update and Importing do. This will give visibility as to their progress.
Personally, I would rather not be restricted to running just one at a time.
I really agree - actually I started the job - and it never finished - and I did not know. I had to make a ticket and realized this. Even bigger problem with this update/job, is that you open an update of a large number of fx. Items that results in many pings towards your order system... If this make any sense... I think it is very important that I am informed that the job is still running and when it have finished.