Messages
The Cron module accepts messages through governance proposals only.MsgAddSchedule
Creates a new schedule through governance proposal.MsgRemoveSchedule
Removes an existing schedule through governance proposal.MsgUpdateParams
Updates the module parameters through governance proposal.State
Schedule
The primary state object in the Cron module:MsgExecuteContract
Defines the contract and the message to execute:ExecutionStage
Defines when messages will be executed in the block:Params
Module-wide parameters:ScheduleCount
Tracks the number of current schedules:Query Methods
Params
Returns the module parameters. CLI Usage:Schedule
Returns a specific schedule by name. CLI Usage:Schedules
Returns all schedules with pagination support. CLI Usage:Events
The Cron module does not emit any custom events. Schedule execution and management operations are logged but do not generate blockchain events.Metrics
The Cron module collects several metrics for monitoring:execute_ready_schedules
(histogram): Time taken to execute all ready schedulesschedule_count
(gauge): Current number of active schedulesschedule_executions_count
(counter): Total schedule executions, labeled by success/failure and schedule name
Client
Query Commands
Theneutrond
CLI provides commands to query the Cron module:
Governance Proposals
Since the Cron module is governance-gated, schedules can only be managed through governance proposals:API Endpoints
gRPC Service
HTTP REST Endpoints
GET /neutron/cron/params
- Get module parametersGET /neutron/cron/schedule/{name}
- Get specific scheduleGET /neutron/cron/schedule
- Get all schedules