Legacy Dev Forum Posts

 View Only

Sign Up

Are PATCH requests locking?

  • 1.  Are PATCH requests locking?

    Posted 06-05-2025 18:17

    square_eyes | 2020-04-30 01:56:06 UTC | #1

    We have an odd situation where con participant attribute data is not being written.

    We are really stumped.

    Our PATCH gets a 202, the attribute keys are written with blank values (where there should be strings). This worked until about a week ago. Then suddenly the blank values. The PATCH response body even includes the received values.

    Testing the the API explorer shows no unexpected results in our Dev Org. Indeed our Dev Org works with our remote Oauth Client too, as expected.

    Hence the thought it may be a race condition, overwrite, or locking issue in Prod.

    There are two other places in the PureCloud IVR that participant attributes are written. But it's a separate KVP.


    square_eyes | 2020-04-30 03:26:11 UTC | #2

    We resolved our issue. I'm guessing PATCH isn't locking by nature (as opposed to PUT).

    As it happens we found the issue further downstream with the attributes being set explicitly as blank, instead of "Value not specified". So in effect the data was being overwritten.


    system | 2020-05-31 03:26:17 UTC | #3

    This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.


    This post was migrated from the old Developer Forum.

    ref: 7677