bug: Failed to parse Teams notify

**Describe the bug** After setting up and saving the information for Teams notify for a service, I get the following error when I try to edit the service again: Failed to parse notify. [ { "code": "custom", "message": "Expected a 32-character hex string.", "path": [ 0, "url_fields", "altid" ] } ] **To Reproduce** Steps to reproduce the behavior: 1. Create a incoming webhook connector in Microsoft Teams 2. Edit service 3. Fill out all of the necessary information for Teams Notify based on the newly created webhook 4. Save the service 5. Edit the service again **Expected behavior** It should parse notify without any issues **Screenshots** <img width="2568" height="1572" alt="Image" src="https://github.com/user-attachments/assets/a01d92e0-c1a4-48c4-bb95-c1f6445c6f9d" /> **Desktop (please complete the following information):** - OS: Linux Debian 13 - Browser: chrome **Additional context** I confirmed that the altid is a 32-character hex string when I inputted it. I also sent a test message before saving it and the message sent successful. In the config.yaml file, it shows the 32 character string but in the web ui, it shows that it is just "secret." Microsoft is also discontinuing the incoming webhook connectors this year and is shifting to workflows which have a different URL format.