@Valerie_Wollinger_WMDE any chance you can collab with Dan to get some content for this email? :) You can drop it here in the comment

Dear Wikibase.cloud user,

Thanks for creating a Wikibase instance on Wikibase.cloud! That was at least 30 days ago. We couldn't help but notice that your Wikibase instance remains empty, so we're checking in to see if we can help.

If you're still planning to use Wikibase for your project but just haven't gotten around to doing so, no worries -- feel free to ignore this email.

Are you having trouble getting started? We have some resources that might help:

• Getting started
• Data modeling
• Learn by example
• Get your questions answered: check the FAQ, ask us or ask the community, either on Telegram or the mailing list

Have you reconsidered using Wikibase for this project? We'd love it if you'd tell us why. (You can delete your empty Wikibase(s) from your dashboard.)

Thanks for using Wikibase Cloud!

@danshick-wmde Hi Dan! I noticed one little thing about the email that there's no mentioning of which wiki is empty. One user can have up to 6 wikis running so it's best to mention it somewhere before the user decided to delete it.
And it's totally doable in the code. Do you think it's a viable option?

In T344689#9226273, @dang wrote:

@danshick-wmde Hi Dan! I noticed one little thing about the email that there's no mentioning of which wiki is empty. One user can have up to 6 wikis running so it's best to mention it somewhere before the user decided to delete it.
And it's totally doable in the code. Do you think it's a viable option?

Well sure! If @Evelien_WMDE wants that, then I'd say add the Wikibase name like this: "We couldn't help but notice that your Wikibase instance $WIKIBASE_NAME remains empty..."

Sounds good, thanks for the suggestion @dang :)

https://github.com/wbstack/api/pull/656

For the one who will pick this up. There are still a few things I couldn't finish before I go:

• Check the notification running in WikibaseNotificationSendRecordJob.
• Fix the test for the Job, I couldn't get it done sorry.

@Evelien_WMDE Just to check what you expect is the following story true:

Wiki is made 29 days ago and is still empty: nothing is sent
One day passes and the wiki is now 30 days old and empty. A Notification is sent on this day.
Another 30 days pass and the wiki is still empty. We don't send any more notifications because this wiki was already notified before.

@Tarrow Correct, you get a cookie
Only additional logic applies to Wikibases that have sat empty for months now. They don't have empty=30 but empty=>30. They are a one-off exception and just get notified upon release of this notification.

relevant side info: currently there seem to be 157 wikis to which the current criteria fits (created at least 30 days ago and not once edited since) and thus which owners we expect to be emailed once this gets deployed.

query used for this info:

Wiki::join('wiki_lifecycle_events', 'wikis.id', '=', 'wiki_lifecycle_events.wiki_id')->where('first_edited', null)->where('wikis.created_at', '<=', '2023-10-15 12:57:44')->count()

I just tried to simulate running this SendEmptyWikiNotificationsJob locally for 200 wikis and it worked fine, but bear in mind that the real environment differs quite a bit from the local setup. Nonetheless I assume that sending ~160 mails like that at once will work.

Here's a screenshot of how the email a user receives looks like (this can be tested in staging with engineering assistance once its deployed):

Job fails to run on staging so reverted:

[2023-11-17 11:39:00] staging.ERROR: Failure processing wiki então.carolinadoran.co for EmptyWikiNotification check: Trying to get property 'first_edited' of non-object                                                                   
[2023-11-17 11:39:00] staging.ERROR: Executing Job '' failed. {"exception":"[object] (Exception(code: 1): Executing Job '' failed. at /var/www/html/app/Providers/AppServiceProvider.php:32)                                               
[stacktrace]                                                                                                                                                                                                                               
#0 /var/www/html/vendor/laravel/framework/src/Illuminate/Events/Dispatcher.php(404): App\\Providers\\AppServiceProvider->App\\Providers\\{closure}(Object(Illuminate\\Queue\\Events\\JobFailed))

issue appears to be that code fails to take into account the possibility that LifeCycle events may not yet be generated

PR with fix for the issue above: https://github.com/wbstack/api/pull/686
(wikis without lifecycle events won't get queried)