That’s twice now that my bot’s programming has been deleted without me knowing why.
So I’ve recreated it twice now. It’s a daily bot, which posts the same topic every day, only the title date changes.
Could you tell me what’s causing my problem?
Thanks in advance.
For additional context, we noticed that scheduled post work usually fine, but the issue mentioned above seems to happen when we try to use the “picture upload” feature with “host on my instance” checked
Is there anything in the logs around the time it was successfully posted the last time? It works by executing the task and then scheduling it again. Or did other jobs disappear as well?
I’m sorry I can’t tell you. I’m a mere user.
Are you using the instance hosted by me at https://schedule.lemmings.world/ or a self-hosted instance?
I’m using your instance.
I’m doing a major rewrite that should (among others) fix this issue, though it’s gonna take me a few more days.
Oh, that’s great news!
It should be fixed now, can you try? Also note that I accidentally deleted all previously set schedules, so if you had something recurring set up there, it’s gone.
I’ve prepared an initial post plan with an external image. When I checked, I saw that the image was not taken into account. So I deleted it and redid it with an image to be uploaded by my instance. Now it sees the image.
We had the same problem when running it in docker. The dev runs theirs on bare metal I think (no docker) and theirs doesn’t have that problem. We switched to using their instance for a while before figuring out another solution.
What solution, if I might inquire?
Just an API call on a cron schedule 😀
It was much harder for me to figure out than your Lemmy-Schedule, but so far so good. Pros and cons to both!
Ah, good old cron!
Anyway, I’m in the middle of a significant rewrite that should fix most of the issues, do you want me to ping you once it’s done so you can give it another try?
Yep, gotta love cron.
Sure, always interested in new developments.
Ooooooooooooooook. Summary of operations:
1/ the day before yesterday, I recreated the schedule for the bot (for 7am yesterday morning)
2/ yesterday morning, my bot created the topic at the said time
3/ this morning, I checked at 6.45am and the schedule is still there
Temporary conclusion:
it’s during the SECOND creation that the scheduler gets stuck in the carpet and makes the schedule disappear.
Action: this morning, I recreate a schedule WITHOUT IMAGE. We’ll see the day after tomorrow.Well well well.
For the second time in a row, the program went without an image.
As my mate @Camus@jlai.lu surmised, it would seem that image management is the problem. This morning I recreated a new schedule, this time with an externally hosted image. We’ll see how it goes tomorrow.
---
EDIT
I’ve checked the scheduler and it says the thread has no image. Strange.Last update :
As I thought, the scheduler doesn’t know how to handle externally hosted images, despite the editable field suggesting that you can add any URL.
Too bad :/
