[GNC] Since last run... errors

[Adrien Monteleone]

That’s not an error.

It is the ’Since Last Run’ Dialog telling you that those two Scheduled Transactions need to be created. (you don’t have them set to automatic)

The second one is telling you that it needs a value for a variable.

You won’t find any of those transactions, because they haven’t been created yet.

But the second pop-up *is* an error message.

It is telling you it can’t find the referenced accounts in the scheduled transactions it is trying to create.

You likely moved or deleted the accounts after creating the scheduled transactions.

Open the Scheduled Transaction editor, edit the problematic transaction templates and make sure each split has a properly assigned valid account.

Note, I had a bug filed that one couldn’t fix this situation, and allegedly that bug has been addressed. I haven’t tested it yet. If you get further errors trying to fix the Scheduled Transaction(s), then you might have to delete them and re-create them.

Regards,
Adrien


> On May 20, 2020 w21d141, at 8:07 PM, Ronald Wiplinger <ronald at elmit.com> wrote:
> 
> I am using GNUcash for a few weeks and when I start the program a popup
> window shows me some errors. I have no idea how to solve this.
> 
> I shows:
> v  Alexander's contribution
>    06/06/20                      To-Create
> v  house rent
>    09/04/20                      To-Create
>        (null) -> TWD                   (Need Value)
> ....
> 
> The list goes on, always telling me:
>        (null) -> TWD                   (Need Value)
> 
> I cannot find the transaction in any account.
> I tried to add a value where it says Need Value. To find it easy later I
> choose 99999 as value.
> 
> After I click OK I get another pop up, telling me:
> 
> Invalid Transactions
> Unknown account for guide
> [ab745cddc36 ... ], canceling SX
> [Alexander's contribution] creation.
> Unknown account for guide
> [ab745cddc36... ] caneling SX [house rent] creation.
> ....
> 
> Needless to say, but next start of GNUcash gives me the same problem.
> 
> How to fix this?