# Can no longer edit a routine

**URL:** <https://forum.cursor.com/t/can-no-longer-edit-a-routine/171677>\
**Category:** Bug Reports\
**Tags:** automations\
**Created:** [September 14, 2026, 10:32pm UTC](https://forum.cursor.com/t/can-no-longer-edit-a-routine/171677 "2026-09-14T22:32:47Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![kevinn](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/kevinn/32/101206_2.png) [@kevinn](https://forum.cursor.com/u/kevinn)\
**Post date:** [September 15, 2026, 3:26am UTC](https://forum.cursor.com/t/can-no-longer-edit-a-routine/171677/8 "2026-09-15T03:26:25Z")

</div>

Hey @Shaun_Bowe, thanks for the report. There are two separate things happening here.

Two separate things are happening here. The Edit button now opens a pre-filled message in the Bot conversation by design. Sending it is the current way to ask the Bot to change a routine.

The missing webhook URL, key, and Authorization header matches a known issue with server-managed routines. It is not caused by your account or setup. Recreating the routine will not help, and the Bot cannot retrieve the key through chat.

For now, the available alternatives are a scheduled routine that polls the external source or a narrowly scoped Slack message routine. We’re tracking this issue, and I’ll update this thread when there is progress.

For now, the practical alternatives are a scheduled routine that polls the external source or a narrowly scoped Slack message routine. This is the same issue discussed here: [Desktop Grok Bot webhook routine shows no POST URL / crsr\_ key (Windows 0.47.0)](https://forum.cursor.com/t/171324)

---

_[View the full topic](https://forum.cursor.com/t/can-no-longer-edit-a-routine/171677)._
