despite the author and public in the same

[elsadek (via Magnolia Forums)]

When activating changes from author, an error araises:<br/>
[code]Caused by: info.magnolia.cms.exchange.ExchangeException: 1 error detected:
Message received from subscriber: Activation refused due to request arriving too late or time not synched between author and public instance. Please contact your administrator to ensure server times are synced or the tolerance is set high enough to counter the differences.[/code]

[Antti Hietala (via Magnolia Forums)]

[quote]Activation refused due to request arriving too late[/quote]

See: Instances are not in sync
http://documentation.magnolia-cms.com/display/DOCS/Instances+are+not+in+sync

--Antti

[elsadek (via Magnolia Forums)]

How could the both instances have different times when they are in the same machine.

[Antti Hietala (via Magnolia Forums)]

Did you try increasing the activationDelayTolerance? The configuration node does not exist by default, the 30 sec default tolerance is set in code. When you create the node and increase the timeout, restart the server to have the value picked up.

As to reasons why activation between two instances on the same server can time out:
* It's possible you activated so many nodes that the later ones timed out.
* In Magnolia 4.5.15 and earlier, the timestamp on author was set _before_ the activation data was collected to a temporary file. In a large activation with lots of binary content, the collecting takes time and the 30 sec default tolerance is easily exceeded. If you run 4.5.15 or earlier this may be the reason. In 4.5.16 the timestamp setting was moved to after the temp is collected. http://documentation.magnolia-cms.com/display/DOCS45/Release+notes+for+Magnolia+4.5.16

--Antti