By default, =condor_annex= will configure your annex's instances to terminate themselves after being idle for =0.25= hours (fifteen minutes). This is intended to help you conserve money in case of problems or an extended shortage of work. As noted in the example output above, you can specify a max idle time (in decimal hours) with the =-idle= flag. =condor_annex= considers an instance idle if it's {link: http://research.cs.wisc.edu/htcondor/manual/v8.6/3_7Policy_Configuration.html#37887 unclaimed}, so it won't get tricked by jobs with long quiescent periods.
+{subsection: multiple annexes}
+
+You may have up to fifty (or fewer, depending what else you're doing with your AWS account) differently-named annexes running at the same time. Running =condor_annex= again with the same annex name before stopping that annex will both add instances to it and change its duration. Only instances which start up after an invocation of =condor_annex= will respect that invocation's max idle time. That may include instances still starting up from your previous (first) invocation of =condor_annex=, so be sure your instances have all joined the pool before running =condor_annex= again with the same annex name if you're changing the max idle time. Each invocation of =condor_annex= requests a fixed number of instances of a given type; you may specify either or both with each invocation, but neither will change either about the previous request.
+
{section: Monitor your Annex}
You can find out if that instance has successfully joined the pool in the following way.
