You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

OIC Schedule API update failing with "input string error for time"

edited Feb 23, 2026 4:51AM in Integration 5 comments

Summary: When we are trying to use OIC Schedule update/add schedule its failing with error as "

"detail":"","status":"HTTP 500 Internal Server Error","title":"For input string: '2026-02-22'","type":"https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.5.1"


Content (please ensure you mask any confidential information):

API used: PUT

/ic/api/integration/v1/projects/{projectId}/integrations/{id}/schedule

Payload used:

{ "name" : "Schedule INT001_TEST_SCHEDULE_01_00_0000", "scheduleTZ" : "Asia/Hong_Kong", "scheduleTZDisplayName" : "Hong Kong Standard Time", "startDate" : "2026-02-22|00:30:00", "icalExpression" : "FREQ=DAILY;INTERVAL=1;BYHOUR=00;BYMINUTE=30;BYSECOND=0;"}

Full Error:

CloudInvocationException [ Fault Details : <ns0:APIInvocationError xmlns:ns0="http://xmlns.oracle.com/cloud/generic/rest/fault/REST/UpdateSchedule"> Server Error</ns0:title><ns0:errorCode>500</ns0:errorCode><ns0:errorPath>&lt;![CDATA[InboundJaxrsResponse{context=ClientResponse{method=PUT, uri=https://design.integration.ap-singapore-1.ocp.oraclecloud.com/ic/api/integration/v1/projects/ENVIRONMENT_UTILS/integrations/INT001_TEST_SCHEDULE%7C01.00.0000/schedule?integrationInstance=oic-devsi2-axrjuvpys69n-si, status=500, reason=Server Error}}]]&gt;</ns0:errorPath><ns0:instance>&lt;![CDATA[{"detail":"","status":"HTTP 500 Internal Server Error","title":"For input string: '2026-02-22'","type":"https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.5.1"}.The 500 Internal Server Error is a very general HTTP status code that means something has gone wrong on the server side, but the target service could not be more specific on what the exact problem is. Try invoking the target service using cURL. If the problem persists, contact the target service admin.]]&gt;</ns0:instance></ns0:errorDetails></ns0:APIInvocationError> ]

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!