Answers.Body: <p>After testing, here is how it works.</p>
  
  <p>If we use again my example with twice the same event date <strong>3rd of April</strong>:</p>
  
  <p>Status 1: from membership date to start date<br/>
  Status 2: from start date to end date.</p>
  
  <p>Status 1 will change <strong>by the end</strong> of the 3rd of April which means start date from the previous status is "Master" and start date lasts 24 hours. Status 2 will appear on the 4th of April. And this is not related to cron Job.</p>
  
  <p>So if you want to start Status 2 on the 3rd of April at 00h00'00", for example if an Insurance is running from this date or if the member has to be of legal age, then set the end event of Status 1 on start date and -1 Day.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-12-04T19:44:24.837Z
Answers.Text: hmm interesting. good you found a workaround. but am wondering if there isn't something else we are missing here but i don't feel i have fully grasped the workflow
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-12-04T09:48:31.850Z
Answers.LastActivityDate: 2019-12-04T09:48:31.850Z
Answers.UserDisplayName: Guillaume Sorel
Body: <p>I have simple membership statuses that say:
  Status 1: from membership date to start date
  Status 2: from start date to end date.</p>
  
  <p>On start date, the membership has changed from not member to member but the status stayed on Status 1. (I have set the cron every hour so it would be updated the way it should).</p>
  
  <p>When is the time limit: 00h00mm00ss or a 24hour period?</p>
  
  <p>How does it work in CiviCRM?</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-12-03T10:39:22.507Z
Comments.Text: I believe that the status changes 1 day after. So if the start date is today then tomorrow the status is updated.
Comments.UserDisplayName: Jaap Jansma - CiviCooP
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-12-03T10:44:44.343Z
Comments.Text: thanks Jaap. I'll check tomorrow.
Comments.UserDisplayName: Guillaume Sorel
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-12-03T21:48:33.613Z
Comments.Text: there is a Scheduled Job that runs - i think the default is nightly but you can set it more often
Comments.UserDisplayName: petednz - fuzion
Tags: <civimember>
Title: How long is start date? 00h00mm00ss or a 24hour period?
ThreadText: # How long is start date? 00h00mm00ss or a 24hour period?
  
  (Asked by: username_0 on 2019-12-03)
  
  I have simple membership statuses that say:
  Status 1: from membership date to start date
  Status 2: from start date to end date.
  
  On start date, the membership has changed from not member to member but the status stayed on Status 1. (I have set the cron every hour so it would be updated the way it should).
  
  When is the time limit: 00h00mm00ss or a 24hour period?
  
  How does it work in CiviCRM?
  
  **Tags:** civimember
  
  > **Comments:**
  > **username_1**: I believe that the status changes 1 day after. So if the start date is today then tomorrow the status is updated.  
  > **username_0**: thanks username_1. I'll check tomorrow.  
  > **username_2**: there is a Scheduled Job that runs - i think the default is nightly but you can set it more often  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2019-12-04. Score: 1 | Accepted answer
  
  After testing, here is how it works.
  
  If we use again my example with twice the same event date **3rd of April**:
  
  Status 1: from membership date to start date  
  Status 2: from start date to end date.
  
  Status 1 will change **by the end** of the 3rd of April which means start date from the previous status is "Master" and start date lasts 24 hours. Status 2 will appear on the 4th of April. And this is not related to cron Job.
  
  So if you want to start Status 2 on the 3rd of April at 00h00'00", for example if an Insurance is running from this date or if the member has to be of legal age, then set the end event of Status 1 on start date and -1 Day.
  
  > **Comments:**
  > **username_2**: hmm interesting. good you found a workaround. but am wondering if there isn't something else we are missing here but i don't feel i have fully grasped the workflow  
  
  ---
  
  