Permission Error When Updating Microsoft Teams Connection URL

[hopewise]

Environment:

Keep version: [0.46.2]
Deployment: [Docker]

Problem:
When updating an existing Microsoft Teams connection URL in Keep (due to Microsoft Power Automate's trigger URL deprecation on November 30, 2025), I receive the following error:

Connection Problem
[Errno 13] Permission denied: '/state/keep_teams_a1b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6'

Steps to Reproduce:

• Navigate to existing Microsoft Teams connection in Keep
• Attempt to update the webhook URL with the new Power Automate trigger URL
• Save the connection
• Error occurs

Connection Problem
[Errno 13] Permission denied: '/state/keep_teams_a1b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6'

Current Workaround:
Creating a new Microsoft Teams connection with the new Power Automate URL works successfully. However, this requires manually updating all workflows/alerts that reference the old connection.

Expected Behavior:
Should be able to update the existing Microsoft Teams connection URL without permission errors.

Questions:

• Is this a known issue with state file permissions in Keep v0.46.2?
• Is there a recommended way to update Microsoft Teams connection URLs without recreating connections?
• Could this be related to file locking or permissions in the /state/ directory?
• Is creating a new connection and migrating workflows the recommended approach, or should updating existing connections work?
• Has this been fixed in newer versions of Keep?

Additional Context:

• The error specifically references the state file for the Teams connection (keep_teams_*)
• No permission issues when creating new Microsoft Teams connections
• Only occurs when modifying existing connections
• Running Keep in Docker with standard configuration
• Issue triggered by Microsoft's Power Automate trigger URL migration requirement

[dosubot[bot]]

This permission error is likely related to how Docker handles file ownership and permissions for the /state directory, especially when updating existing files. It's not a documented or widely reported issue in Keep, but similar problems can occur if the user inside the container doesn't have write access to files created by a different user or container instance. Creating a new connection works because it creates a new file with the correct ownership, while updating tries to modify an existing file that may have mismatched permissions or ownership due to previous container runs or upgrades reference.

There isn't official documentation or a recommended workflow for updating Microsoft Teams connection URLs without recreating connections. No fixes for this specific issue appear in newer versions or recent pull requests. The best workaround is to ensure the /state directory and its contents are owned by the same user that the Keep container runs as. You can do this by adjusting the ownership of the /state directory on the host, or by running the container as root (not generally recommended for production) or matching the container's user ID to the file owner.

Updating existing connections should work, but this is a classic Docker file permission scenario. If you continue to encounter this, recreating the connection and updating workflows is the most reliable workaround until a more robust fix or documentation is available.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}