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.

You are viewing a single thread.
View all comments View context
1 point

It’s broken for Lemmy versions newer than 0.19.3, or is it broken even for you even on 0.19.3?

permalink
report
parent
reply
2 points

Initial test is good on our instance on 0.19.5. Thanks again.

permalink
report
parent
reply
1 point

We’re on 0.19.5, but it has been working great from schedule.lemmings.world.

I saw there’s an update, so I’ll give that a go and report back later.

Thanks!

permalink
report
parent
reply
2 points

Yep, it should fix the issue. Though I still have no idea what caused it. But well, sometimes it really is as simple as updating your dependencies.

permalink
report
parent
reply

Lemmy Schedule

!schedule@lemmings.world

Create post

This is an official support forum for Lemmy Schedule.

Links:

Community stats

  • 6

    Monthly active users

  • 29

    Posts

  • 11

    Comments

Community moderators