Details
-
Type:
Improvement
-
Status:
Resolved
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 5.0.rc1
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
A list of all jobs should be displayed. Jobs are either timers or async messages (an icon to indicate that would be nice).
A sys admin should be able to
- View list of job failures
- Retry failed jobs
Jobs can have exceptions. The exception property contain the stacktrace.
Jobs with property retries == 0 are to be considered as in a DLQ. Those should have an action enabled to retry the job. It would be great if the system allowed for easy selection of multiple jobs for retry. That might happen e.g. if a mail server is temporary down.
Beginning to think about User journey here. From my discussion with Tom yesterday, there are the following use cases:
A user visiting the Jobs queue might want to do several things:
1) Clear a backlog (a backlog is any message based job, since they should be run instantly, or any timer past its execution time). Actions:
View/filter jobs table
run/retry one or many jobs
determine how many more retries are available.
2) Clear the DLQ: The Dead Letter Queue is where jobs go after they have failed and their retry count has reached zero. Actions:
View/filter jobs table
View exception data to determine why jobs have failed
Retry failed job(s)
3) View timer jobs.
View/filter jobs table
Determine when jobs will run
Manually run one or more jobs without waiting for the timer to finish. (Using retry API)