Could not act on confirmation when confirming incoming offers

[MrInka]

Hey, 

I know this is an old topic, so I did quite a bit of research.  

 

- I am not using a confirmation key twice (I guess?), since I am only calling direct confirmations for offers that just got accepted - also not accepting multiple offers at once in one bot.

 

- I am not being rate-limited (Yes, I have two bots running parallel in separated scripts, but both start up delayed and both confirmationcheckers are disabled (just like polling for offers)).

 

- I am defenitly logged in.

 

- I have seen "The tag for accepting needs to be allow, not accept." on another post, same error. This doesn't apply to me right?

 

 

 

Here is how I am handling offers:

manager.on('newOffer', function(offer) {
        if(acceptArray.indexOf(offer.id) >= 0){    //Check if the offer ID is listed in an array
            console.log("Offer ID is listed! Accepting!")
            offer.accept(function(err) {
                    if (err) { 
                            console.log("Accepting failed:" + err);
                    } else {
                            console.log("Accepted! (" + offer.id + ")")
                            setTimeout(function(){    // Small delay between accepting and confirming. Does this make sense?
                                community.acceptConfirmationForObject(config.identitysecret, offer.id, function(err){
                                    if(err){
                                        console.log("Confirming failed: " + err);
                                    } else {
                                        console.log("Confirmed! (" + offer.id + ")");
                                    }
                                });
                            }, 250);                                        
                    }
            });
        } else {
            console.log("Offer ID unknown. Ignoring this trade!")
        }
});

It doesn't fail for every offer, but sometimes!  

 

Is there anything else I could do to fix this? 

 

 

 

- Thanks!

 

 

 

 

 

Edit: Just came to my mind. My bot is running on a RaspberryPi:

Raspberries dont have a battery, so they can't keep up with the system time when they are fully turned off. Sometimes after starting it, it has problems to update the system time automatically. Sadly I dont know if this problem occured together with the problem I described above.  

 

Just generally: Could a wrong system time cause a "could not act on confirmation" error in some way? 

 

 

 

 

Edit2: Okay, also happens on my windows PC where the system time is 100% right. Any more ideas?

Edited July 31, 2017 by MrInka

[Dr. McKay]

If your system clock is wrong, that will definitely cause errors.

[MrInka]

Yup and thanks for the reply, I read about that by now.  

 

Sadly, I tested and this also happens when running the bot on my Windows PC, where the system time is 100% right.  

 

What else could cause this error?