Showing results for 
Show  only  | Search instead for 
Did you mean: 

This product reached the end of support date on March 31, 2021.

Publish scripts and config to agent-initiated communication robot

Dynatrace Guide
Dynatrace Guide


What is the default schedule/behaviour of an agent-initiated communication robot to update its script libraries and configurations ?

I have 1 robot working on an internet line - outside of the company firewall - so it is configured to use agent-initiated communication.

A couple of days ago, a monitored website changed, and the script/autocheck configuration updates were published to all (internal) agents.

All robots, including the external one perform a daily reboot for sanity purposes, but still after a couple of days, the script/configuration changes are not applied to the external robot.

So - the question - how often does the robot check for/download configuration changes in such cases, and where can this setting be changed to occur more often, or even, how can we achieve this on-demand ?

All answers are greatly appreciated.


Dynatrace Pro
Dynatrace Pro

Hi Jeroen,

the Agent should definitely not take days to apply the changes, nor should it require a reboot to apply the change.

I'd recommend to get in touch with support because that looks like a problem to me.

Once you get it resolved, we'd all appreciate an update on what the problem was.




Hi Jeroen, I believe even if dealing with agent-initiated communication you still have to publish changes to those robots. I used to work with a customer who had external robots that were also agent-initiated communication aligned and I recall still having to publish to the external agent-initiated robots as well.

This is correct, Steve. Jeroen, did you Publish after your changes for the agent-initiated Agents? If not, please do so and let us know if that is successful. Thanks!

Dynatrace Guide
Dynatrace Guide

Hi, during configuration publishing, we always publish to all robots.

As for the (Active) script publishing, we still use the old style of doing - we manually copy the testpartner db and ini file to the external robot.

Normally the first part should be enough I think to handle any schedule changes AND AutoCheck configurations, but apparently this robot is having difficulty to synchronize those (xml) files.

I'll take it up with support to assist me in finding the issue.