Answers.Body: <p>Sorry for the slow response - I am just now seeing this question.</p>
  <p>The status <em>should</em> be: &quot;Setting changes were saved on 2020-05-04, data calculation will be performed on every cron run.&quot; I'm not sure why that confusing message is displayed instead. Do you have the summary fields cron job enabled? If not, that could be the problem. When the summary fields cron job runs, it should create the triggers and calculate as needed.</p>
  <p>For testing, you could also try updating the settings manually. In other words, where it says &quot;When should these changes be applied?&quot; - select &quot;When I submit this form&quot;. Then click the save button.</p>
  <p>If the status still says the triggers are not created, trying de-selecting one of the fields in the configuration and saving. Then, re-select and save again (summary fields pays attention to whether there are any changes in the list of selected fields and will only update the triggers if there is a change).</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-04-23T12:10:31.477Z
Answers.Text: I've done these steps on 5.0.0. The "Status of current settings" and "Data update method: Cron Job" are correct. but no triggers for Triggers for civicrm_contribution or Triggers for civicrm_participant:  which I am using are enabled. 
  
  What are the findings of this extension on a large db of around 800K records? I've been very selective and using the simplified fields for performance considerations.
Answers.UserDisplayName: Andy Burns
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-04-23T12:10:49.240Z
Answers.Text: The Scheduled job says e.g. Finished execution of Call SumFields.Gendata API with result: Success (a:1:{i:0;s:89:"Original Status: scheduled:2021-04-23 06:32:07, New Status: scheduled:2021-04-23 07:47:03";})
Answers.UserDisplayName: Andy Burns
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-05-03T15:12:29.770Z
Answers.Text: No triggers should be enabled if your data update method is "When the cron job runs". Triggers are only enabled if the update method is "instantly".
Answers.UserDisplayName: Jamie
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-01-15T15:44:19.500Z
Answers.LastActivityDate: 2021-01-15T15:44:19.500Z
Answers.UserDisplayName: Jamie
Body: <p>On the extensions admin screen I see</p>
  
  <p><a href="https://i.sstatic.net/sK1gl.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/sK1gl.png" alt="enter image description here"></a></p>
  
  <p>I tried following <a href="https://civicrm.stackexchange.com/questions/17799/triggers-for-summary-fields-disappeared">this solution</a> but rebuilding triggers had no effect. </p>
  
  <p>How do I get the triggers to be enabled? The cron job <em>Call SumFields.Gendata API</em> says it is successful and runs every hour. </p>
  
  <blockquote>
    <p>Parameters parsed (and passed to API method): 
    a:1:{s:7:"version";i:3;}</p>
    
    <p>Full message:  Finished execution of Call SumFields.Gendata API with
    result: Success (a:1:{i:0;s:89:"Original Status: scheduled:2020-05-04
    15:33:23, New Status: scheduled:2020-05-04 15:37:48";})</p>
  </blockquote>
  
  <p>That is the only cron job I see.</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-06-29T06:00:01.020Z
Comments.Text: I am having the same problem. Andy, did you find a solution to this?
Comments.UserDisplayName: Josh
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2021-01-15T16:35:46.140Z
Comments.Text: I've created this issue on github: https://github.com/progressivetech/net.ourpowerbase.sumfields/issues/83
Comments.UserDisplayName: TwoMice
Tags: <summaryfields><trigger>
Title: Summary Fields triggers settings not enabled
ThreadText: # Summary Fields triggers settings not enabled
  
  (Asked by: username_0 on 2020-05-04)
  
  On the extensions admin screen I see
  
  [![enter image description here](https://i.sstatic.net/sK1gl.png)](https://i.sstatic.net/sK1gl.png)
  
  I tried following [this solution](https://civicrm.stackexchange.com/questions/17799/triggers-for-summary-fields-disappeared) but rebuilding triggers had no effect.
  
  How do I get the triggers to be enabled? The cron job *Call SumFields.Gendata API* says it is successful and runs every hour.
  
  > Parameters parsed (and passed to API method):
  > a:1:{s:7:"version";i:3;}
  >
  > Full message: Finished execution of Call SumFields.Gendata API with
  > result: Success (a:1:{i:0;s:89:"Original Status: scheduled:2020-05-04
  > 15:33:23, New Status: scheduled:2020-05-04 15:37:48";})
  
  That is the only cron job I see.
  
  **Tags:** summaryfields, trigger
  
  > **Comments:**
  > **username_1**: I am having the same problem. Andy, did you find a solution to this?  
  > **username_2**: I've created this issue on github: https://github.com/progressivetech/net.ourpowerbase.sumfields/issues/83  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_3 on 2021-01-15. Score: 1
  
  Sorry for the slow response - I am just now seeing this question.
  
  The status *should* be: "Setting changes were saved on 2020-05-04, data calculation will be performed on every cron run." I'm not sure why that confusing message is displayed instead. Do you have the summary fields cron job enabled? If not, that could be the problem. When the summary fields cron job runs, it should create the triggers and calculate as needed.
  
  For testing, you could also try updating the settings manually. In other words, where it says "When should these changes be applied?" - select "When I submit this form". Then click the save button.
  
  If the status still says the triggers are not created, trying de-selecting one of the fields in the configuration and saving. Then, re-select and save again (summary fields pays attention to whether there are any changes in the list of selected fields and will only update the triggers if there is a change).
  
  > **Comments:**
  > **username_0**: I've done these steps on 5.0.0. The "Status of current settings" and "Data update method: Cron Job" are correct. but no triggers for Triggers for civicrm_contribution or Triggers for civicrm_participant:  which I am using are enabled.   What are the findings of this extension on a large db of around 800K records? I've been very selective and using the simplified fields for performance considerations.  
  > **username_0**: The Scheduled job says e.g. Finished execution of Call SumFields.Gendata API with result: Success (a:1:{i:0;s:89:"Original Status: scheduled:2021-04-23 06:32:07, New Status: scheduled:2021-04-23 07:47:03";})  
  > **username_3**: No triggers should be enabled if your data update method is "When the cron job runs". Triggers are only enabled if the update method is "instantly".  
  
  ---
  
  