corestack_ crons_ validate
Check a scheduled task.
When to use it
Check a cron schedule and / or command before saving it: when it would next run, warnings, and anything the platform refuses. Nothing is saved.
A command with a password or key written in it (export DB_PASSWORD=…, mysql -p…, curl -u user:…, --password=…, an Authorization: Bearer … header, a URL with a password) answers valid: false with the reason in errors.command, because the command is stored with the scheduled task, and corestack_crons_update refuses it (invalid_arguments). The placeholder corestack_crons_get shows for a hidden command ([hidden: …]) is not a command either: it answers valid: false with the same reason the update gives. A command one of the site's tasks already has, checked unchanged, answers valid: true with a warning in warnings: it is kept when it is saved back unchanged. Put the value in a file on the site and read it from there instead, for example set -a; . /.
Ask for it
Using the Corefinity MCP server, call corestack_crons_validate with site_id 4211, schedule */15 * * * *, command php bin/magento cron:run. (Check a scheduled task.) Tell me what it returned.Inputs
The command, run as the site's web user. Up to 20,000 characters.
A five-field cron schedule or a preset such as @daily. Up to 200 characters.
At least 1.
Example call
{
"name": "corestack_crons_validate",
"arguments": {
"site_id": 4211,
"schedule": "*/15 * * * *",
"command": "php bin/magento cron:run"
}
}If it is refused
| Reason | What to do |
|---|---|
invalid_arguments | The arguments do not match the tool's input schema, or the Control Panel refused a field. Fix the fields named in the answer and call again. |
tenant_mismatch | The object does not exist or the token may not see it. Check the id. |
scope_required | The token lacks a scope this call needs. Open the link in the answer to add it, then call again. |
pin_refused | The grant is limited to chosen clusters, sites or environments, and this call is outside them. Open the link in the answer to widen it. |
rate_limited | Too many calls. Wait for the number of seconds the answer names. |
temporarily_unavailable | The Control Panel could not answer just now. Nothing was started; try again shortly. |
internal_error | Something went wrong on our side. Quote the trace id to support. |