Old token being used when new token was updated last night, why might that be?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-28-2025 05:05 AM
Hello,
For the dynatrace Oneagent integration, there is a token that is stored in a property in the sys_properties table on servicenow.
There is a scheduled job which runs at 3:15 am and there is a script include in it and then the integration uses that token. It is due to expire today as the user who made it is leaving today.
The token was upgraded last night in prod. The new token was generated by a service account, but when the scheduled job ran last night, it used both old and new token. That's what they are seeing on the dynatrace side. Why might that be?
I have checked the script includes, business rules, client scripts, transform scripts, UI actions etc and that token property is not being called anywhere else except for the 1 script include in the scheduled job, so why might this be happening?
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-28-2025 05:58 AM
Very helpful information.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-28-2025 07:05 AM - edited 03-28-2025 07:08 AM
Did both API calls were successful with old and new token?
Are you sure that both API calls are from the same instance and what is the time gap between two API calls?
Thanks,
Swathi
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-28-2025 08:20 AM
yes both API calls are successful and they are being made at 3:16 am when the scheduled job executes.
The old one is set to expire today as the user is leaving today.
