-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AECU is executed too often in AEMaaCS #228
Comments
The scripts need to be developed that they can run multiple times, yes. |
@nhirrle hmm it seems to be very consistent in always executing it multiple times and it doesnt seem to detect correctly (anymore?) that this is happening :/. You can see it in my screenshot, almost all runs are like this. Could this maybe be improved somehow? Its really hard to write scripts that executes on multiple pages to not come into a state that its doing duplicate modifications and throwing exceptions around that. You’d have to refresh your resourceresolver constantly |
@royteeuwen can you provide some more details? is the script with the always selector? and any idea if this is with a recent aemaacs release? would be good if it can be verified with some sample scripts on a sandbox |
@nhirrle no the script is not with an .always. selector. You can see that in my screenshot it starts the run of the same scripts twice (at 12:56:16 and 12:56:20) and didn't detect that it was already running. When the run of 12:56:20 started, one of the 7 scripts was already done by the run of 12:56:16, so that's why it states that there are only 6 scripts. The result of the two runs happening at (almost) the exact same time is the following for the second run executing the same script at the exact same time:
The script itself is not an .always, and the script executes the following, where it finds like at least 1000 results with the query:
The thing I could do to "improve" it, is moving the session.save() inside the .each and doing a refresh every time. But this would make the script run a lot longer. |
Thanks for the details. I will have a look beginning of next week. there is also a related ticket #227 |
Hi @royteeuwen This requires major changes and a new release. Unfortunately I can only commit on a fix within the next 4 weeks. |
@nhirrle OK! Just make sure to not create the job on every AEM instance, because then you would still execute the rules x times |
one further observation: exception thrown during startup |
When using AECU in AEMaaCS, there seems to be an issue that the scripts are executed too many times. See screenshot showing an example of this. Probably because there are multiple author instances executing it in the same time?
The text was updated successfully, but these errors were encountered: