Even as a developer I find it really hard to understand the UX in the CMS.
Have a look here:
I have no idea what most of these fields mean.
What I would suggest:
show only the key details
create an advanced tab with all the details
provide better messages about why a job has not run.
Provide a sentence about what it does... E.g. This job will run in 6 minutes. It will [e.g. clear your cache so that you ....].
have a system to work out if the cron job to run them is running - e.g. every time it is pinged, set a value in a cache so that you can work out how often the jobs are being "polled".
Even as a developer I find it really hard to understand the UX in the CMS.
Have a look here:
I have no idea what most of these fields mean.
What I would suggest:
show only the key details
create an advanced tab with all the details
provide better messages about why a job has not run.
Provide a sentence about what it does... E.g. This job will run in 6 minutes. It will [e.g. clear your cache so that you ....].
have a system to work out if the cron job to run them is running - e.g. every time it is pinged, set a value in a cache so that you can work out how often the jobs are being "polled".