|
@@ -41,7 +41,7 @@ Looks up the user by login or ID and posts into the DM room.
|
|
|
|
|
|
|
|
## Cron delivery patterns
|
|
## Cron delivery patterns
|
|
|
|
|
|
|
|
-- **Split content destination from report destination.** Content goes out via `chatto_send_room`/`chatto_send_dm` called BY the job prompt; the cron `deliver` field routes only the final confirmation/report (e.g. `deliver: "chatto-platform:<room_id>""` — resolve the ID via `chatto_list_rooms`). A `deliver` target without a `:thread_id` segment lands in the channel's main chat.
|
|
|
|
|
|
|
+- **Split content destination from report destination.** Content goes out via `chatto_send_room`/`chatto_send_dm` called BY the job prompt; the cron `deliver` field routes only the final confirmation/report (e.g. `deliver: "chatto-platform:<room_id>"` — resolve the ID via `chatto_list_rooms`). A `deliver` target without a `:thread_id` segment lands in the channel's main chat.
|
|
|
- Pattern: prompt says "post X to room Y via chatto_send_room, mention @user, then answer with a short confirmation" — `deliver` stays `origin` or points at a separate admin channel.
|
|
- Pattern: prompt says "post X to room Y via chatto_send_room, mention @user, then answer with a short confirmation" — `deliver` stays `origin` or points at a separate admin channel.
|
|
|
- Test any redesigned flow with `cronjob_manage action='run'` before the next scheduled fire.
|
|
- Test any redesigned flow with `cronjob_manage action='run'` before the next scheduled fire.
|
|
|
|
|
|