Hey guys - We checked into this further, and I've updated the Seamless Deployment section with more information about what happens in the deploy/undeploy process. The key is to set the delay parameter to a long enough time (seconds) to allow transaction processing to finish before the previous revision is undeployed. So technically, yeah, it's still possible to get 5xx errors if transaction processing takes longer than the delay. So just set a really long delay. There's no limit on the number of seconds you can set, and there are no performance implications.
Provide your email address if you wish to be contacted offline about your comment.We will not display your email address as part of your comment.
Type the characters you see in the picture above; if you can't read them, submit the form and a new image will be generated. Not case sensitive.