Skip to content

cron add should require --agent flag or warn when not specified #42196

@padixa

Description

@padixa

When creating a cron job with cron add, the --agent flag is optional. If not specified, the job runs with the default agent (main), which can cause confusion.

Problem:

  • A cron job related to a specific agent was executed by the wrong agent
  • The delivery channel is separate from which agent executes the task
  • Without explicitly specifying --agent, there is no way to know which agent will run the task

Suggested fix:

  1. Make --agent required when creating cron jobs, OR
  2. Show a warning when --agent is not specified

This would prevent accidental execution by the wrong agent.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions