Notification works in test mode but not in "real life" mode

[smileBeda]

I've a notification set up:

• system wide link to posts://my-domain/hooks/XXX
• system wide body:

{
  "attachments": [
    {
      "text": {{ ("##### " ~ watch_title ~ " has been updated\n" ~ diff) | tojson }},
      "actions": [
        {
          "name": "Update Docker Container",
          "integration": {
            "url": "http://actions-api:8000/docker/update/{{ watch_title | lower }}?token=changeme",
            "context": {
              "image": "{{ watch_title | lower | replace(' ', '-') }}"
            }
          }
        }
      ]
    }
  ]
}

• Plain Text
• GROUP CSS/JSONPath/JQ/XPath Filters

jq: "**New Version:** `\(.tag_name)`"
jq: "**Read more:** [Release notes](\(.html_url))"

• GROUP notification body

{{ current_snapshot | replace('""','\n') | replace('"','') }}

The notification works perfectly fine when I test the notification both in global settings or single item. However in GROUP test it says Error: No Notification URLs set/found and when I await an actual update the notification fails with:

2025/11/11 16:37:43,000 - SENDING - null
2025-11-11 16:37:44,780 - WARNING - Exception in custom HTTP handler: 400 Client Error: Bad Request for url: https://my-domain/hooks/XXXX?format=text
2025-11-11 16:37:43,679 - DEBUG - Loaded Custom HTTP - POSTS URL: posts://

I don't understand why - the only thing that I changed from when it was working is the global URL, and by as far as I understand the GROUP should inherit from GLOBAL just like the single item does?!

yet, it seems it does not and thus why it fails?

[smileBeda]

After some days off and on debugging I finally solved this one:

1. There is a BUG in ChangeDetection, the TEST notification will simply never send if you test in GROUP and have GLOBAL url setting but no GROUP.
2. Unrelated to that, I had to:

• move the GROUP notification body to GLOBAL as part of my new GLOBAL body, and leave GROUP empty
• adjust GLOBAL json a tad
• leave JQ filters in GROUP

That really was it, I just should NEVER even have tried "test notification" because... well, it simply does not work lol, one can test as much one wants. Real-life notifications then worked once fixed.