I believe I found my issue.

It appears I had a hook upon clockout that was causing issues.  So sorry to
bother everyone.

On the plus side, I learned some lisp debugging skills.

Thanks again.

On Tue, Dec 13, 2016 at 10:13 AM Mark Wood <mjwood0@gmail.com> wrote:

> I did a little more digging.  I too can get it to work correctly, so long
> as there is no Default Clock task identified.
>
> However, if I create a default clock task, it appears that the :clock-in
> property is ignored.
>
> I'll try to dig into it a little more, but I can reproduce it every time
> when there is a default clock.
>
> Thanks again for looking at it.
>
> On Tue, Dec 13, 2016 at 8:09 AM Nicolas Goaziou <mail@nicolasgoaziou.fr>
> wrote:
>
> Hello,
>
> Mark Wood <mjwood0@gmail.com> writes:
>
> > After recently upgrading to 20161118, I notice that the clock-in property
> > in my org-capture-templates is no longer functioning.  It appears to
> > successfully clock me out of my current task, but that's it.
> >
> > My capture template is:
> >
> > (setq org-capture-templates
> >       '(("t" "Todo" entry (file "/org/refile.org")
> > "* TODO %?\n%U\n" :clock-in t :clock-resume t)))
>
> FWIW I cannot reproduce it, i.e., clock is properly started.
>
> Regards,
>
> --
> Nicolas Goaziou
>
>