Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
C
Core
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 933
    • Issues 933
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • Development
  • Core
  • Issues
  • #168

Closed
Open
Opened Jun 07, 2018 by lolcode@lolcode

If scheduled jobs are run individually nothing is logged to civicrm job log

When running scheduled jobs individually to have greater control over the timing or parameters of those jobs then nothing is logged to the JobLog at least for certain jobs like process_mailing. This leaves the user to implement something else for logging.

I don't agree with this approach because it will push organisations to use custom solutions but it should at least be a documented limitation.

https://docs.civicrm.org/user/en/latest/initial-set-up/scheduled-jobs/#specific-jobs

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: dev/core#168