topic Re: Revisions for key for schema are outdated in Dynatrace API

Revisions for key for schema are outdated

g_kat — Tue, 24 Sep 2024 05:58:36 GMT

Hi,

I am trying to update a metric event through the API, just to enable/disable it.

I initially succeeded to PUT the updated payload and got a 200. But after that, every attempt to modify it results in a 409 Conflict error with the following message:

Revisions: '\n '<some ID>' for key '<some other ID>' for '<schemaid>' are outdated.

The only variable thing in my payload seems to be the update token, which I grabbed from the API tab on the metric event I wanted to modify, and this doesn't seem to change, looks more like a unique identifier and not a nonce.

Has anyone encountered this in the past?

P.S. I face this on Managed, haven't checked if it's the same case on SaaS.

Regards,

George

Re: Revisions for key for schema are outdated

GosiaMurawska — Thu, 02 Jan 2025 15:33:41 GMT

Hi, @g_kat! Have you managed to find the answer to your question? It would be great if you share it with the Community 🙂

Re: Revisions for key for schema are outdated

g_kat — Thu, 02 Jan 2025 16:21:46 GMT

Hi @GosiaMurawska

I ended up automating the procedure with a Python script that invokes the API twice a day to enable/disable the metrics events and I haven't faced this issue as long as it's running(>2 months).

I can only assume that when I did my initial tests I somehow created a corner case condition with my API calls, maybe due to rapid calls on the same schema?.

I never bothered to reproduce it since the script worked.

Thanks,

George