I've deleted them all now but each post is posting three times - what information do you need from me to try to resolve this?

Along with a few fixes that hopefully make docker work again, I've added two new features:

• when you paste a link into the URL field, the title of the page will be fetched and filled into the Title field (if the Title field is empty)
• you can now use counters in your titles

Counters are basically named variables that increase after each successful post, those are mostly useful for recurring post. They can start at any value and by incremented by any value (well, except zero). They can be injected using the same syntax as dates:

• #[Counter('counter-name')]#

Just a reminder that you can use #[InjectDate('Y-m-d')]# syntax to insert the date at the time of posting (of course replace Y-m-d with your desired format)

Despite this account being marked as bot, its human owner is typing this post out right now.

Oops! An Error Occurred

The server returned a "500 Internal Server Error".

Something is broken. Please let us know what you were doing when this error occurred. We will fix it as soon as possible. Sorry for any inconvenience caused.

I am letting you know now! Trying to schedule a post from lemmy.zip with this account, successfully logged in on the scheduler, to !otomegames@ani.social. I receive this error.

Hi!

I love the app, but have frequent trouble with my instance not accepting some nsfw webp. Imgur doesn't allow NSFW content, but catbox.moe does.

Would it be possible to integrate catbox.moe uploading + linking into the app?

I don't really know what to look for in the logs, but with some guidance maybe we can figure this out. Here's how it typically goes:

Set up daily recurring auto-post at sub.wetshaving.social. It works for about 1-2 weeks, then stops.

I set the entire server to restart every 3 or 4 days, which makes Lemmy Schedule stable for longer, but still every week or two it will stop working.

The solution is some sort of combination of restarting the Docker stack (Lemmy Schedule and Redis) and/or opening the Lemmy Schedule web interface and logging in, logging out, refreshing, logging back in, whatever it takes. The need to load the web page is odd, like it reminds Lemmy Schedule somehow that "oh yeah, there are posts to post".

A lot of times when I log in to fix it, the scheduled post does not appear in the to-do list. We have a weekly post that stays in the to-do list, but not until I reload, log out, etc. will the daily post eventually find itself and reappear in the list.

When it starts working again, it typically spits out the posts that it missed, sometimes in duplicate.

Any ideas?

Since version 1.6.0, Lemmy Schedule supports Lemmy 0.19.3.

You might need to log out and log in if it does not work.

Hello @rikudou@lemmings.world, I hope you are doing well.

We just updated our instance (https://jlai.lu) to 19.3 yesterday, and noticed that today the scheduled posts had disappeared. I tried to create them again, but got this error:

Just wanted to report this to you, let us know if at some point you are able to fix it.

Have a good one!

New version has been released, it contains one small bug fix where the app wouldn't clean up list of old job ids and thus making the listing slower and slower as you posted more posts. Now it correctly cleans up any job id that does not exist anymore from list of your jobs, thus making it significantly faster.

If you've self-hosted using Redis, you might have not noticed it because Redis is quite fast, so nothing much changes for you.

I've added a new experimental feature to Lemmy Schedule, currently only available if you're self-hosting and enable the feature using the FLAG_COMMUNITY_GROUPS environment variable (set it to 1 or something).

Community groups allow you to define a group of communities which then can be a target when creating a post. Meaning you can create a group that consists for example of 5 different "world news" communities and then you don't have to remember which ones you usually post to, you just post to the group and it will get resolved to actual community names automatically.

The feature will be available on https://schedule.lemmings.world once I finish it, currently it's not very polished (error handling needs some work, other than that it should work well).

Hi @rikudou@lemmings.world ! I manage a bot for !parentalite@jlai.lu and your schedule app usually post 3 times. Today, the application posted the same post 9 times ! (I've left them for you to see).

Hi ! One of our community c/ has a duplicate of their scheduled posts by parentbot : https://jlai.lu/post/2008603

They deleted their other posts. Dunno if it is helpful, but we can do few tests if needed. Thank a lot :)

Currently if we accidentally create a schedule then there is no way to edit it (if we were to make a mistake), and then we have to completely redo the post

I mod !edm@reddthat.com and want to have a post on tuesday's that increments every tuesday. My titles are: [Trance Tuesdays #1] and i would like to have the number increment so it counts up from X.

Hi, thanks so much for this tool. I've had your post saved for a while and I finally got around to checking it out and it's great. Just wondering if I'm missing it, but is there a way to edit a scheduled post? Like to change the title or text? Thanks again!

Hello @rikudou@lemmings.world ,

The tool is still working great, now I had another question for you: would it be possible to have the option to automatically unpin recurring post, once a new one is created? I have daily threads that I would like to keep pinned, once at a time.

Currently, I haven't seen that option, as the current unpin option is for a specific date, not a recurring time

Thank you in advance!

Say i schedule a link of an article to be posted. While the time until it gets posted the link gets already posted in the same intended community but just by another user. Once time's up my post would basically look as a duplicate. Is there a way to make the scheduler detect if the post already exists in the target com and that way doesn't post instead. (even if it needs to post, then find out that it is posted -cause it would appears as crossposted to X-com, at least thats how i find out when posting manually- and then just decide to delete instead. even in a timeframe of 30 seconds or so no one would probably even catch up to that. That would be nice and would spare the mods of deleting duplicate posts and doesn't make me look as a com spammer lol. Thanks.

I just want to post at GMT+0 (no energy saving hour) time.

A new feature has been added, this one is especially useful for recurring post - it allows you to add the date and/or time of the post to the title.

As an example you can use this exact post which should contain a date that looks something like 2023-10-03 23:15:00+0200 (note that the second will most likely be different, because the scheduler is not exact to the second).

This is how I've written the title in Lemmy Schedule: New version - add date to the post title (example: #[InjectDate('Y-m-d H:i:sO')]#).

You may notice the #[InjectDate('Y-m-d H:i:sO')]# - this is an expression that will be evaluated at the time of posting. Currently only the InjectDate expression is supported and it takes exactly one parameter. If you're a programmer, you probably recognize it, it's a format for the date. Just beware that it uses the PHP date format which might differ slightly from your favorite language.

If you're not a programmer, the documentation is not that hard - you see a letter (like F) and its description (A full textual representation of a month, such as January or March). When you include F in the parameter, it means it will be replaced with current month name (October). If this is too hard for you and you want it for one or few posts, tell what you want the title to look like and I'll write it for you.

Note that there's a preview of what the title looks like:

You'll also know if you've provided something that looks like it should be an expression but is not recognized:

Here are some examples:

• Weekly discussion - week ##[InjectDate('W')]# - Weekly discussion - week #40
• Monthly discussion - #[InjectDate('F')]# #[InjectDate('Y')]# - Monthly discussion - October 2023
• Monthly discussion - #[InjectDate('F Y')]# - equivalent to the above, just wanted to show that you can use it multiple times
• Daily thread - #[InjectDate('d.m.Y')]# - Daily thread - 03.10.2023

Let me know what you think!

Hello,

First of all, thanks for the tool, it works great! I would like to discuss with you the possibility to add something like "02-10-2023" to the title of recurring posts. That would be helpful for the daily posts in !casualconversation@lemmy.world

I've released version 1.2.1 which contains one small fix. Previously, when you created a post with an image and posted it to multiple communities, it would get deleted immediately after creating the first post. Now the image should be available for 5 minutes after the original post time.

I'm constantly missing new posts from smaller communities I moderate (like this one, sorry pals, won't happen anymore) so I've added a new feature to Lemmy Schedule.

You can schedule getting notified of any new posts from any specific community you desire. This feature makes the most sense if you enable recurring schedule, but I've made it possible to use a one-time schedule even though I can't really see a use-case. But hey, maybe you will!

The reports will be sent by @UnreadPostReportBot@lemmings.world, make sure you don't block it.

The feature is available for people who self-host as well, in that case you'll have to create your own bot account and put its JWT token (and instance) into the configuration.

You can of course create more than one schedule for a single community, meaning you can get reports at a granularity that the recurring scheduler doesn't report - if you create a recurring job for every hour of the day, you'll get a report every hour of every day.

Let me know how you like the new feature!

You can now select where you want to upload an image when scheduling a post. Current options are the target instance or Imgur.

This is for two reasons:

1. Some instances have very small limits for image files
2. By uploading to different hosts you don't add to the instance admin's storage cost

If you know any other host you'd like to see supported, do let me know!

Hey, nifty piece of kit you made here, and thank you for it. Only problem is that I don't actually see it being posted.

I installed it all via docker compose and it seem to work fine. I'm able to open the app, log into lemm.ee with my credentials, then schedule a post. It then simply clears from the queue at the right time without the post happening.

The redis docker logs aren't showing anything. Here is what I have from the lemmy-schedule docker logs: 192.168.1.50 - - [17/Sep/2023:15:43:50 +0000] "GET /post/create HTTP/1.1" 200 22270 "http://192.168.1.20:8000/post/list" "Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/112.0" 192.168.1.50 - - [17/Sep/2023:15:43:50 +0000] "POST /en/_components/ScheduleComponent/setTimezoneAsString HTTP/1.1" 200 1934 "http://192.168.1.20:8000/post/create" "Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/112.0" 192.168.1.50 - - [17/Sep/2023:15:44:24 +0000] "POST /post/create/do HTTP/1.1" 302 652 "http://192.168.1.20:8000/post/create" "Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/112.0" 192.168.1.50 - - [17/Sep/2023:15:44:25 +0000] "GET /post/list HTTP/1.1" 200 2583 "http://192.168.1.20:8000/post/create" "Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/112.0"

In the above I set something to post at 15:56. It clears from the queue and nothing further is put into the logs.

Any troubleshooting I should try?

Has anyone experienced getting duplicate posts? every now and then I get a duplicate post and I'm not really sure how to go about debugging it

I've got one post scheduled every day to post in lotrmemes@midwest.social for the account https://lemm.ee/u/Wikischedule, but as you can see from the account linked, it misses quite a few days at a time, and has missed the last 5 days in a row.

Let me know if there's any more info I can provide about the issue ~