One problem that can cause a missing transaction is if the SLR created the
transaction, then GnuCash was improperly closed without saving the file,
most likely by turning off the computer without closing the program or by
losing access to the media by removing a USB key or ethernet cord.

David Carlson

On Sat, Nov 16, 2019 at 12:04 PM Jack Slater <theillini...@gmail.com> wrote:

> Manually showed/did nothing.
>
> It is active and shows last run 11/08 and next run 12/08.
>
> I entered manually and will watch the 12/08 transaction to see what
> happens.
>
> On Fri, Nov 15, 2019 at 3:54 PM Adrien Monteleone via gnucash-user <
> gnucash-user@gnucash.org> wrote:
>
> > Manually executing the Since Last Run dialog from the Actions > Scheduled
> > Transactions menu should trigger any overdue transactions to fire. The
> > dialog will show any reminders of upcoming transactions if you created
> > rules for such reminders, as well as showing you which ones were created
> > and the option to review those created transactions.
> >
> > If this menu option doesn’t fire the overdue transactions, double check
> > the Scheduled Transaction itself in the editor to make sure it is listed
> as
> > active and see when was the last occurrence and the next scheduled
> > occurrence.
> >
> > If there is just one period where it did not fire, but it did so both
> > before and after said period, then you might have to manually create that
> > missing one. The easiest way to do that is to select one of the existing
> > example transactions, right-click and choose “Duplicate Transaction” and
> > edit the date/num accordingly.
> >
> > Regards,
> > Adrien
> >
> > > On Nov 15, 2019 w46d319, at 1:29 PM, Jack Slater <
> theillini...@gmail.com>
> > wrote:
> > >
> > > David -
> > >
> > > So I have to create a NEW scheduled transaction in order to get the
> > missing
> > > one in the ledger? There is no way to force the old scheduled
> transaction
> > > to show in the ledger?
> > >
> > > Also - whats causing this? Bug? Its happened more than once now, on
> > > different scheduled transactions.
> > >
> > > Jack
> >
> > _______________________________________________
> > gnucash-user mailing list
> > gnucash-user@gnucash.org
> > To update your subscription preferences or to unsubscribe:
> > https://lists.gnucash.org/mailman/listinfo/gnucash-user
> > If you are using Nabble or Gmane, please see
> > https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
> > -----
> > Please remember to CC this list on all your replies.
> > You can do this by using Reply-To-List or Reply-All.
> >
> _______________________________________________
> gnucash-user mailing list
> gnucash-user@gnucash.org
> To update your subscription preferences or to unsubscribe:
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> If you are using Nabble or Gmane, please see
> https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
> -----
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.
>


-- 
David Carlson
_______________________________________________
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Reply via email to