[BUG] "File Does Not Exist" Error when Posting Content

[bmanfacts]

Hello Martin!

Reporting an issue when I use the Post Images Module.

Here's what I expect to happen:

I have a folder containing 800 photos. I have the module set to post one unique piece of content per day. When i do this, I expect the posting module to run for 800 days @ 1 post/day. [Relevant settings: Upload-1, Unique uploads only-checked]

However, what happens is the following: after about 15-45 days, the content no longer posts. When i look into the logs, it says [in this example]:

Posting: xxx/800
* File does not exist: C:\Users\xxx\AppData\Local\Temp\1\xxx

However, the original content folder I have the module set to has all the content. SO its not posting from there for me. I know the bot historically did this posting from temp files, but for some reason, now its disruptive to get a content cycle completed without complications.

Could you look into this?

Sending logs which show several accounts dealing with this. All accounts displaying this have not come anywhere close to finishing its content set.

Log ID: 80227

[martin@rootjazz]

let me check on this.. should be a quick solution

[martin@rootjazz]

Posting: xxx/800
* File does not exist: C:\Users\xxx\AppData\Local\Temp\1\xxx

Log ID: 80227

ok strange, code doesn't show images being moved to TEMP folder for storage until posting...

errrr

[martin@rootjazz]

C:\Users\martin\AppData\Roaming\rootjazz\Instadub\watchcmdsaved\

that's the folder used

%appdata%\rootjazz\instadub\watchcmdsaved

then when it comes to posting, it will take that image, use the temp dir for quick modifications to file (pre-processing if applicable) and for making the bytes unique, but no way the temp folder is being emptied during this, it's seconds and what the temp folder is intended for...

[martin@rootjazz]

is it possible you set this action up LONG time ago, when the program was using TEMP folder and not app data folder? It's the only thing I can think of. Unless you doing something different with the setup I am not doing which is exposing this bug, but all seems to be working fine for me.

I'll add some logging improvements for next update to find out more

[bmanfacts]

is it possible you set this action up LONG time ago, when the program was using TEMP folder and not app data folder? It's the only thing I can think of. Unless you doing something different with the setup I am not doing which is exposing this bug, but all seems to be working fine for me.

I'll add some logging improvements for next update to find out more

I checked for that possibility by relaunching actions in the most recent updates. This happens on with an account that posts images with no modifications. Still happens consistently. The example spans across several accounts. And this typically begins after 15 days as noted in the OP. I believe something related to that explanation you provided is the cause, since the content posts as expected until it doesn't at a long enough time period.

[martin@rootjazz]

ok to confirm.

The WATCH FOLDER action runs, content detected and the POST action created for 15 (or whatever days time).
When this time comes, the action logs out the TEMP file location doesn't exist.


But it doesn't affect all images, the initial ones detected and scheduled all work fine.


--------------------------------

But that makes no sense. The TEMP FOLDER is not used, the watch folder doesn't save there. The action doesn't have the image logged as to be posted from there. I cannot think how it can happen.

I made changes to the logging when you first reported this, if you have updated recently, submit logs please and I will take another look to see if I can find something


HELP > LOGS > SUBMIT

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


If you didn't update, please do:
https://rootjazz.com/instadub/updatetesting.html

Then when happens again, submit logs

[bmanfacts]

The WATCH FOLDER action runs, content detected and the POST action created for 15 (or whatever days time).
When this time comes, the action logs out the TEMP file location doesn't exist.


But it doesn't affect all images, the initial ones detected and scheduled all work fine.

Correction: The **********POST IMAGES******* action runs, content detected and the POST action created for 15 (or whatever days time).
When this time comes, the action logs out the TEMP file location doesn't exist.
--------------

Updated to current version and like clockwork the issue popped up.
Sending logs of Last day
Should be able to search for the issue again.
Logs: 16202

[martin@rootjazz]

thanks for logs, I will check through.

<edit>

Apologies realised you sent this ages ago and I never replied

[martin@rootjazz]

your logs show

Line 747: 00:43:12: * File does not exist: C:\Users\Administrator\AppData\Local\Temp\1\4ff227b2-4092-41b1-9502-40117a14b441.jpg
Line 758: 00:43:13: * File does not exist: C:\Users\Bul*** ***ga\AppData\Local\Temp\567a8e70-4f8d-402e-9d81-221f16ba904e.jpg

Note two paths for appdata.

You use multiple users to log into the machines?


Shouldn't make a difference. Still the logs don't have the information, indicating why the actions have the images stored in TEMP dir. The program doesn't put them there. It just doesn't. But clearly the action has them there. So it makes no sense.

I will need to investigate further