Answers.Body: <p>Yes, this is a regression bug caused due to recent change to datetime on Activity forms. This is now fixed at <a href="https://github.com/civicrm/civicrm-core/pull/13497" rel="nofollow noreferrer">PR#13497</a> and should be part of 5.11 release. You can either wait for 5.11 release or apply patch from <a href="https://patch-diff.githubusercontent.com/raw/civicrm/civicrm-core/pull/13497.patch" rel="nofollow noreferrer">here</a>.</p>
  
  <p>Thanks</p>
  
  <p>Pradeep</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-02-13T00:34:54.030Z
Answers.Text: Thanks @pradeep for you quick response. Will definitely try the patch.
Answers.UserDisplayName: FullStack-Dev
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-02-13T00:31:35.303Z
Answers.LastActivityDate: 2019-02-13T00:38:58.547Z
Answers.LastEditDate: 2019-02-13T00:38:58.547Z
Answers.UserDisplayName: Pradeep Nayak
Body: <p>I get yellow screen with message as <code>One of parameters (value: 2019-02-13 00:25:00) is not of the type Timestamp</code> when i close the ongoing case. This use to work on 5.9.0 but recent upgrade to 5.10 stopped working. Any clue?</p>
  
Tags: <civicase>
Title: After Upgrade to 5.10 unable to close Case
ThreadText: # After Upgrade to 5.10 unable to close Case
  
  (Asked by: username_0 on 2019-02-13)
  
  I get yellow screen with message as `One of parameters (value: 2019-02-13 00:25:00) is not of the type Timestamp` when i close the ongoing case. This use to work on 5.9.0 but recent upgrade to 5.10 stopped working. Any clue?
  
  **Tags:** civicase
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2019-02-13. Score: 1
  
  Yes, this is a regression bug caused due to recent change to datetime on Activity forms. This is now fixed at [PR#13497](https://github.com/civicrm/civicrm-core/pull/13497) and should be part of 5.11 release. You can either wait for 5.11 release or apply patch from [here](https://patch-diff.githubusercontent.com/raw/civicrm/civicrm-core/pull/13497.patch).
  
  Thanks
  
  Pradeep
  
  > **Comments:**
  > **username_0**: Thanks @pradeep for you quick response. Will definitely try the patch.  
  
  ---
  
  