Repeated notifications when the "console" is configured as a notificationExecutableId

[f000]

First of all, thank you for this excellent project, it is greatly appreciated!

Expected Behavior

When configured, ACM should send exactly one Slack notification per each execution in the Console. This is important for security and auditing purposes.

Current Behavior

When console is included in the notificationExecutableIds of the dev.vml.es.acm.core.code.Executor configuration, then ACM continuously sends Slack notifications with the output "Hello World!" multiple times per minute.

This happens even when:

• No code is currently running in the Console
• The last executed Console code is completely different from "Hello World!"

Simply opening the ACM interface is enough to trigger this behavior - no user interaction is required. As a result, the configured Slack channel is flooded with "Hello World!" notifications.

Steps to Reproduce

1. Configure and enable Slack notifications in ACM
2. Add console as one of notificationExecutableIds of dev.vml.es.acm.core.code.Executor OSGi config
3. Reload the ACM interface
4. Wait a short amount of time
5. Observe your Slack channel being flooded with "Hello World!" ACM notifications
6. Navigate to another AEM section (e.g. Sites)
7. Observe that notifications stop

Context (Environment)

• Local AEM SDK 2025.10.22943
• AEMaaCS 2025.11.23482

[krystian-panek-vmltech]

Simply I haven't respected the case when somebody could want to include console in notifications. Console main purpose is for developing scripts, do ad-hoc things... And whenever you execute something you see its results immediately in the same gui thus notification is redundant. As far as I understand your case this is won't fix from my side. Simply you should exclude console id from notifications.

[f000]

OK, I see your point, but it was meant more as a specific setting for production, where we want to have a detailed overview of what is happening in ACM. For script development and testing, a Dev or Local environment would be used where console notifications would not be enabled...

[krystian-panek-vmltech]

Probably parse execution need to be excluded. Maybe it's not right now. I will check this.

[krystian-panek-vmltech]

hey @f000 , the issue should be resolved now by #285 , releasing soon ;) have a great day, thanks for reporting this!