When you include a date value that includes time zone-specific formatting in a REST API query, a non-200 response code is seen.
For example: 0000-00-00T01:02:03+09:00 specifies a local time zone format. The REST API does not accept this type of input.
If you enable trace, you might see the following trace statements if an invalid date format is supplied in the request:
[3/6/13 17:04:37:650 EST] 000000f5 DateUtils 1 Invalid value in time
[3/6/13 17:04:37:885 EST] 000000f5 DateUtils 1 Error converting twClass value to date: com.ibm.bpm.wle.api.InvalidDateException: CWTBG0546E: Invalid date received '0000-00-00T01:02:03 09:00', date has to be in ISO-8601 format 'yyyy-MM-dd'T'HH:mm:ssz'
The IBM Business Process Manager REST API only accepts date values that are in a UTC format. In return, it only responds with UTC-formatted date values. It is up to the caller of the REST API to perform any necessary time zone conversions before a request is sent to the server and when the response is received from the server. Any time zone-specific formatted values results in an HTTP error. Most likely it results in a HTTP 400 Bad Request error.
Resolving The Problem
To resolve this issue, you must make changes to the application that is utilizing the REST API in its integration All date values that are used as input must not include time zone-specific information, but they must use UTC formatting. An example of a valid date format is: 0000-00-00T01:02:03Z
15 June 2018