View Issue Details

IDProjectCategoryView StatusLast Update
0003316Composrcorepublic2018-02-11 01:09
ReporterPatrick SchmalstigAssigned ToChris Graham 
SeverityFeature-request 
Status resolvedResolutionfixed 
Product Version 
Fixed in Version 
Summary0003316: 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 0003314
TagsNo tags attached.
Time estimation (hours)2
Sponsorship open

Relationships

child of 0002794 resolvedChris Graham CRON management in admin zone 

Activities

Chris Graham

2017-07-09 15:55

administrator   ~0005161

Last edited: 2018-02-05 17:00

View 2 revisions

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 Patrick Schmalstig 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 0002794
2018-02-05 16:58 Chris Graham Relationship deleted child of 0002794
2018-02-05 17:00 Chris Graham Note Edited: 0005161 View Revisions
2018-02-10 00:35 Chris Graham Relationship added child of 0002794
2018-02-11 01:09 Chris Graham Status non-assigned => resolved
2018-02-11 01:09 Chris Graham Resolution open => fixed
2018-02-11 01:09 Chris Graham Assigned To => Chris Graham