kevshTO wrote: ↑Fri Dec 01, 2017 5:59 am
I am running one instance each of TwitterDub and TumblrJazz concurrently - though there is some crossover in that the apps are both using the same credentials (email addresses, proxies, etc. - I am using the same email address in some cases for both Twitter and Tumblr, along with the associated proxy) and as pointed out I'm having similar issues in TumblrJazz. If you require I can test there and provide details as well.
This won't be a problem. It could be a problem if you tried to open multiple copies of THE SAME program, so tried to open tumjazz 3 times, as all instances would try to read from the same db, try to write to the same db, would lock, hide, repeat files. But that isn't your issue
As for the sequence in TD, here's what I'm doing:
1) Click on Image Tweet tab
2) Select a single account in the bottom pane for this action
3) Click on Dir button and select the image folder to be used
4) Click the Import File button to load the images
4) Click on the Assign Meta button and copy/paste meta details where appropriate, then click Save
5) Enter the # Max Upload and Fluctuate values (typically "3" and "1")
6) Set the Random Pause values (typically "20" to "65" or so)
7) Click the Daily Run checkbox and specify the time (typically "11:00" or so for the first action for an account), specify the fluctuate minutes (typically 65-90 minutes) and select the days (typically 6 days of the week), click Save.
8) Check the Unique Uploads Only box
Many thanks I am testing this now
What then happens is the initial (first scheduled) action will run at the desired time and upon completion create another action shortly after (see the screen shot in my previous post).
this would be correct, on completion the new action should be scheduled for the DAILY RUN time of 11:00 +- fluct. You didn't mention the rescheduled time, I assume it is correct?
To complicate things, I did notice today that two of three "early" Post Images actions (three separate accounts) did not run at all - at least not within the fluctuation time. The one that did run created another upon completion - I didn't note unfortunately the exact time but it was within two hours. The two that didn't run I restarted a little later and upon completion each created an action for the same time the next day (in other words, as expected).
this sounds like the processor is out of sync, but your logs should help me
I will try and replicate now, unless I can cause it, my options to fix are limited.
Please perform the following:
Open the program. Delete or pause all existing actions. If actions are already running due to autorun on startup, disable autorun at startup and restart the app. All actions must be waiting, then pause all (or delete)
Delete existing logs
HELP > LOGS > VIEW
delete all files in the folder that opens
Perform the action:
***
Create the action as you specified above
Run it
Leave the program running, do not add any other actions, do not perform any actions.
Then when teh issue appears, please submit logs again. This will allow me to view ONLY logs related to the issue, sometimes the logs are so detailed trying to spot the error amongst all the useless irrelevant data is impossible
***
PLEASE NOTE: Do not perform other actions at the same time. Only use one thread. Do not run any actions after this action.
Then submit logs:
HELP > LOGS > SUBMIT
and let me know the LOGS ID (just the number part is sufficient)
Regards,
Martin