Confirm the installed capability
Newer source includes PHP script workloads alongside Node.js/Python and WordPress. This is separate from a website's PHP-FPM request handler. Use the exact current application-capabilities response and PHP version list. Earlier kits without the script-schedule helper cannot be made compatible by typing a runtime into a request.
The installation opt-in --php-script-schedules is for a fresh full installation and the exact native-qualified PHP 8.3 helper bundle. It defaults false for legacy installation. Do not use it as an undocumented live retrofit or infer PHP 8.4 capability from unrelated source package declarations.
Create and schedule
Select the active same-account website/application and the advertised PHP script runtime. Review relative entry point, working/document root, supported arguments and resource limits. Staged write-only environment secrets remain private. Use the managed application schedule form for name, five-field cron expression, IANA timezone, overlap policy, timeout, notification and enabled state.
Schedules bind the current parent revision and retained release identity. An application replacement or configuration change must not silently run a stale script under a previous context. A manual run remains a durable task; inspect exit status, stdout/stderr byte counts, truncation, start/finish times and notification status.
Security and recovery
The helper is a typed unprivileged execution boundary, not a browser shell or arbitrary privileged command. Account quotas/cgroup/confinement and current feature/licence rules still apply. Confirm that suspended accounts and invalid parents are denied. Never place a root-only path, shell expansion or private server credential in a public task argument.
Verify and troubleshoot
Test a harmless script on the designated disposable VM, inspect its actual output and verify overlap/timeout behavior. SMTP notification readiness requires both configured transport and a verified recipient. For a missing helper/capability, use the supported kit qualification path; do not copy an executable over a live service or weaken confinement. Current installed application/task isolation and full recovery still need their documented acceptance; source routes and fixtures do not certify production readiness.