send later ignores scheduled time on heroku

[uurcank]

Version:

• listmonk: 2.0.0
• OS: Deployed to Heroku

Description of the bug and steps to reproduce:
Send later sends emails instantly regardless of time selection.

Deploy to Heroku button may be skipping to add background workers. And there is no information in docs how to add later.

[knadh]

The following screenshot is from a Heroku deployment. There is no additional configuration or backround workers (listmonk uses multi-threading) required. Perhaps this has something to do with timezones or 24H time format?

[uurcank]

@knadh I tested this again and it instantly runs the campaign. Scheduling does not work for me. Scheduled for 17 hours later but it was still sent.

Do I need to deploy any recent changes from https://github.com/knadh/listmonk-heroku ?

[uurcank]

[knadh]

You are running v2.0.0, right? Can you try scheduling for day + 1 and see if it still triggers?

[uurcank]

scheduled for +3 days and it still did

[uurcank]

I am on v2.0.0

[uurcank]

here is the output from logs

2021/10/17 11:51:02v2.0.0 (05585b7 2021-09-27T17:59:39Z)
2021/10/17 11:51:02reading config: config.toml
2021/10/17 11:51:02connecting to db: ec2-52-70-120-204.compute-1.amazonaws.com:5432/xxxxx
2021/10/17 11:51:02media upload provider: s3
2021/10/17 11:51:02loaded email (SMTP) messenger: XXXX@email-smtp.us-east-1.amazonaws.com
2021/10/17 22:18:27start processing campaign (Copy of October Digest 2021)
2021/10/17 22:18:27campaign (Copy of October Digest 2021) finished
2021/10/18 06:59:03error registering campaign view: pq: null value in column "campaign_id" of relation "campaign_views" violates not-null constraint
2021/10/18 06:59:15error registering campaign view: pq: null value in column "campaign_id" of relation "campaign_views" violates not-null constraint
2021/10/18 11:07:12start processing campaign (Copy of October Digest 2021)
2021/10/18 11:07:12campaign (Copy of October Digest 2021) finished

[knadh]

This is strange. Can you confirm that the timestamps on the log are correct?

[uurcank]

timestamps in logs seem to be UTC time, not my timezone.

[knadh]

I tried this on a Heroku instance and I'm unable to reproduce the problem.

• Create new campaign. Populate with dummy content.
• Pick a schedule.
• Save changes.
• Click on the Schedule icon on the campaigns list (or the 'Schedule' button the campaign's page)

Can you confirm that you're following the exact steps?

[uurcank]

@knadh I tested it again using your instructions, and it works. So this is a user interface issue. I never considered pressing "save" first. It is not anticipated.

The "Start campaign" button should submit the form and schedule or start the campaign at the same time. Saving is useful to create a draft that you can work on later.

[knadh]

Ah, got it. Fixed the behaviour. Thanks @uurcank