Summary
The Create Workitemand Update Workitem APIs currently reject requests when the dateDue value exceeds the dateExpires value. This validation is being removed.
After this change, the dateExpires field can be set to any time at least one hour after the current time and before the end of the workitem’s lifecycle,independent of the dateDue value. This update provides greater flexibility in configuring workitem expiration while preserving lifecycle constraints.
Affected APIs
HTTP Method | API | Description |
POST | /api/v2/taskmanagement/workitems | Create a workitem |
PATCH | /api/v2/taskmanagement/workitems/{workitemId} | Update the attributes of a workitem |
Effective Date
Thursday, March 12, 2026
Details
The existing behavior enforced a strict relationship between dateDue and dateExpires based on earlier customer feedback. This restriction limited valid use cases.
With this update, customers can configure workitem expiration independently of the due date, as long as expiration remains within valid lifecycle boundaries.
Customer Impact
Previously, requests where dateDue was later than dateExpires were rejected with an error similar to the following:
{
"message": "dateDue cannot be greater than dateExpires. dateDue: 2026-02-06T00:00:00Z, dateExpires: 2026-02-05T00:00:00Z",
"code": "pre.check.value.greater.than",
"status": 409,
"messageWithParams": "{name1} cannot be greater than {name2}. {name1}: {value1}, {name2}: {value2}",
"messageParams": {
"name1": "dateDue",
"name2": "dateExpires",
"value1": "2026-02-06T00:00:00Z",
"value2": "2026-02-05T00:00:00Z"
}
}
This validation is now removed. Requests will no longer fail when dateDue exceeds dateExpires, provided that dateExpires meets the following criteria:
• At least 1 hour in the future, and
• Before the end of the workitem lifecycle.
No breaking changes are expected for existing integrations.
Impacted Resources
Create a workitem: POST /api/v2/taskmanagement/workitems
Update a workitem: PATCH /api/v2/taskmanagement/workitems/{workitemId}
Contacts
Please reply to this announcement with any questions. This helps the wider developer community benefit from the discussion. We encourage you to use this thread before contacting the designated person directly. Thank you for your understanding.