openproject sends emails out properly in general, but for a certain subproject I dont receive any notifications via email, even if I’m explicitly set as a watcher for this project. Is there any known issue regarding this?

Thanks & Best Regards
Qiong

Hello Qiong,

thanks for your question.
I just tried creating and updating a work package in a subproject (with a separate watcher) and I received email notifications (using OpenProject 4.0).
Could you answer a couple of questions to better identify the error:
Does this error happen for all your subprojects?
Which version of OpenProject are you using?
Did you activate delayed job? (otherwise email updates are not sent)
Does the specific subproject where this error occurs have other settings then the other projects / subprojects?

Thanks,
Robin

Thanks for the reply!

The error doesnt happen for all my subprojects. Interestingly enough, email notifications for wiki updates are also working for this specific subproject, but not for work packages.
I’m using OpenProject 3.0.14 (PostgreSQL)
Where do I activate delayed job? I do assume that I activated it though, as email notifications are working for my other subprojects.
no other settings as far as I can see.

I’ll try upgrading to Openproject 4.0 and report back :)
EDIT: okay as far as I can see, there is no documented way to migrate to 4.0 yet

Cheers
Qiong

Hello Qiong,

the command to activate the delayed job (in production) is

RAILS_ENV=production bundle exec script/delayed_job start

To stop it:

RAILS_ENV=production bundle exec script/delayed_job stop

You’re right that this should not be project specific so the error may be caused by something else.
Let’s see if the error still occurs after the update to OpenProject 4.0.

Best,
Robin

Hi, just to check in. THe issue has been resolved by upgrading to OpenProject 4.0.1. Thanks!

Hi, thanks for the update.
Glad to hear it’s working now. :)

I just realized that the delayed task runner is not autostarted on server restart, when I restart the server I need to run the delayed task again.
Is this intended behavior`?