Program crashes how tweet messages start from beginning.

[JasperJones]

Hey Marin,

My Twitter Software crashed, probably because I am running to many applications at once. My question is though, If I had a weeks worth of tweets scheduled and the twitter app closes or crashes when re opened and when the process is started again, does the tweets start from the start again or when left off?

Thanks

[martin@rootjazz]

Depends, did you have unique on? If you did, it will just loop over the previously processed and go back to where you were.

If not, it will start back at the beginning

[JasperJones]

Yes, and it won't post because it is considered a duplicate. A few hours lost there.

[martin@rootjazz]

I don't 100% understand what you are saying. It didn't post the items you had already posted? That is what you wanted? Yes?

[JasperJones]

I create a mass twitter post process, posting every 3600 seconds. After a few hours Twitterdub crashed. The process started all over but since I had unique on it wouldn't repost. No big deal, I am trying to setup a way to be able to post frequently but still also use other processes while posting.

[martin@rootjazz]

when it comes to a post it has posted before, it should be skipped and the next one is attempted straight away with no pause. I think you are saying it does pause, thus you had to wait a long time for it to catch up to where it was,


Can you confirm

[JasperJones]

Yes, this is correct.

[martin@rootjazz]

why did you say

Let me take a look at the code (if you have logs they would be useful)

HELP > LOGS > SUBMIT

then send your logs ID - the first 4 numbers is sufficient (displayed after successful uploading of logs)

[JasperJones]

I did delete all my logs as it adds up in space. I'll see if it happens again in the future if I do post like that again.

[martin@rootjazz]

I just tested posting duplicate tweets and the tweet is ignored and there is NO pause.

So I would need to see your logs showing the pause to try and understand the flow that happens for you. So next time, please submit logs




Regards,
Martin