View Issue Details

IDProjectCategoryView StatusLast Update
3316Composrcorepublic2018-02-11 01:09
ReporterPDStig Assigned ToChris Graham  
PrioritynormalSeverityfeature 
Status resolvedResolutionfixed 
Summary3316: Error catching for CRON
DescriptionCatch errors that are triggered by any tasks that are run by cron_bridge.php: terminate the faulty cron hook, but continue to the next cron hook rather than terminating the entire cron_bridge.
Additional InformationI'm not sure if this idea is even possible to implement or if it is a good idea. However, should this be implemented, it will resolve issues of faulty cron hooks blocking the execution of other cron hooks. This would especially be important for the issue I stated in comments for 3314
TagsNo tags attached.
Attach Tags
Time estimation (hours)2
Sponsorship open

Sponsor

Date Added Member Amount Sponsored

Relationships

child of 2794 ResolvedChris Graham CRON management in admin zone 

Activities

Chris Graham

2017-07-09 15:55

administrator   ~5161

Last edited: 2018-02-05 17:00

I think it's a good idea.

Not a priority for me though, because:
(a) I'd rather just make sure any errors are fixed
(b) v11 has the capability of reducing Composr's error sensitivity which is a pretty major change to our past policy of ultra-sensitivity

Issue History

Date Modified Username Field Change
2017-07-08 02:25 PDStig New Issue
2017-07-09 15:54 Chris Graham Time estimation (hours) => 2
2017-07-09 15:55 Chris Graham Note Added: 0005161
2018-02-05 16:58 Chris Graham Relationship added child of 2794
2018-02-05 16:58 Chris Graham Relationship deleted child of 2794
2018-02-05 17:00 Chris Graham Note Edited: 0005161
2018-02-10 00:35 Chris Graham Relationship added child of 2794
2018-02-11 01:09 Chris Graham Status Not Assigned => Resolved
2018-02-11 01:09 Chris Graham Resolution open => fixed
2018-02-11 01:09 Chris Graham Assigned To => Chris Graham