When sending a larger transaction through to publish, the transaction may appear to fail deployment and shows the following in the publishing queue:
Preparing Deployment Failed Polling for notification for destination: alksdfaalaldfjjfkljlkjseeojvn==has exceeded polling attempts for transaction: tcm:0-12345-66560. |
Increase polling in the transport configuration file, <CMS>\SDL Web\config\cd_transport_conf.xml For instance, this is the default entry and the numbers may need to be raised via a tuning exercise. <!-- Specifies the polling attempts and timeout in minutes and interval between polls in milliseconds --> <Polling MaxAttempts="900" Timeout="15" Interval="5000"/> This setting signifies the time interval between checks for feedback. With the setup above, the poller will check every 5 seconds for the status of each transport package. It will stop polling after 900 tries, or after the combination of attempts and interval which in this case is (900 x 5)/60 = 75 min ( 1 hr & 15 min), or after the assigned interval of 15 minutes. MaxAttempts - The maximum number of polling attempts A transaction will be failed once the first of two limits is exceeded. |
Polling attempts to update transaction status are exceeded, however the transaction may continue deploying and ultimately be successful. |
Also see this Tridion stackexchange post for additional discussion. https://tridion.stackexchange.com/questions/17130/sdlweb8-5-preparing-deployment-failed-due-to-polling-for-notification-for-dest |