Use one disposable schedule
The verified course job was named course-3-first-alarm, used a one-word prompt, fired once, and was deleted by exact ID. The 13 curated jobs were not changed.
Prove the exact prompt first
armaraos message <UUID> "Reply only: scheduled-working"
Never schedule a prompt you have not first proven with a one-shot message. Wrong now becomes wrong repeatedly when nobody is watching.
Read the five cron fields
| Field | Meaning |
|---|---|
| 1 | Minute |
| 2 | Hour |
| 3 | Day of month |
| 4 | Month |
| 5 | Day of week |
*/2 * * * * is a watched classroom test. 0 9 * * 1-5 represents weekday mornings. Real unattended work should start in hours, not minutes.
Create, then verify independently
armaraos cron create <UUID> "*/2 * * * *" "Reply only: scheduled-working" --name course-3-first-alarmarmaraos cron list --json
Create printed Failed: ?, but the named row existed and was enabled. Do not retry a state-changing command until you inspect state, or you may create duplicates.
Watch the last-run field
A timestamp replaced null and next run advanced. That is the reliable proof. The TUI log remained unsuitable as an activity feed, so this page does not simulate one.
Distrust the disable success line
armaraos cron disable <ID>armaraos cron list --json
Disable and enable printed success, but the created job stayed enabled. They are not reliable controls for this job on version 0.8.3.
Remove the exact test loop
armaraos cron delete <ID>
Delete has no undo. Use the ID captured from the named row. The disposable job disappeared and the original curated count returned.
Apply the billing-loop rule
Minute-scale schedules are continuous loops.
Use them only for a watched disposable test, then remove them. Start genuine schedules at hours and re-check the roster before walking away.
Check it / confirm cleanup
Read one untouched schedule.
armaraos cron list --jsonConfirm course-3-first-alarm is absent. Read one existing job's name, enabled field, next run, and schedule without changing it.
A scheduled prompt uses real credentials and can spend money unattended. On this build, do not trust a disable success line without verifying JSON; remove an exact disposable test ID before leaving it.
Troubleshooting for this sitting
| What you see | Likely cause | What to do |
|---|---|---|
Create prints Failed: ? | Known response defect. | Inspect the named row before retrying. |
| Last run remains null | The scheduled minute has not arrived. | Read next run and wait while watching. |
| Disable says success but enabled is true | Verified control defect. | Delete the exact disposable ID before its next run. |
| A duplicate appears | Create was retried after the false error. | Resolve each ID and remove only the duplicates. |