c2c-oerpscenario team mailing list archive
-
c2c-oerpscenario team
-
Mailing list archive
-
Message #05160
[Bug 433395] Re: failing crons must report properly
I would be interested to know an illustrative situation where I can face this on trunk.
Thanks.
** Changed in: openobject-server/trunk
Status: In Progress => Triaged
** Changed in: openobject-server/trunk
Assignee: Jay (OpenERP) (jvo-openerp) => (unassigned)
** Changed in: openobject-server/trunk
Milestone: 6.0 => None
** Changed in: openobject-server/trunk
Assignee: (unassigned) => OpenERP's Framework R&D (openerp-dev-framework)
** Changed in: openobject-server/trunk
Importance: Wishlist => Undecided
--
failing crons must report properly
https://bugs.launchpad.net/bugs/433395
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
Status in OpenObject Server: Triaged
Status in OpenObject Server 5.0 series: Won't Fix
Status in OpenObject Server trunk series: Triaged
Bug description:
currently crons fail quietly
IMHO there should be a default notification function (sending a requst or mail to the job owner od a dedicated user) which runs if the cron job fails.
I see a problem sending requests to the administrator, because this account will not be used regulary