Discobot يقوم بإزعاج مستخدم

Any idea why discobot sent at least 4 of these to the same user over the course of a couple of days?
Apparently even after the user replied with “skip”?
discobot
February 12

Hey @Deena, just checking in because I haven’t heard from you in a while.

  • To continue, reply to me any time.
  • If you’d like to skip this step, say skip .
  • To start over, say start tutorial .

If you’d rather not, that’s OK too. I’m a robot. You won’t hurt my feelings.

Visit Message or reply to this email to respond to discobot, Deena.

In Reply To

discobot
February 12

Sometimes you might want to get a person’s attention, even if you aren’t replying to them directly. Type @ then complete their user name to mention them. Can you mention @discobot in your reply?

Hi! To find out what I can do, say @discobot display help.

It appears the user started the new user tutorial then stopped partway through, causing Discobot to respond to see if the user still wants to engage. What other messages were sent other than the one you showed? What you are sharing here appears to be normal.

He said it was sent 4 times. Maybe sidekiq is borked on his install? That’s all I can think of. Looks like we host it though @justin

Nope all is good here. I checked the PM since it’s on our hosting and it’s because:

  • the user started the tutorial
  • stopped
  • discobot followed up
  • the user said skip
  • discobot went to the next step
  • user stopped
  • discobot followed up
  • user said skip again

It’s possible the thought process was ‘oh skip should stop this’ but instead it advances the tutorial.

Does that sound right @Peter_Galvin?

Ah yes that sounds possible. Will let them know. Thanks.

واحد من مشرفيّ يتلقى رسائل البريد العشوائي من رسالة “الآن بعد أن تم ترقية حسابك، حان الوقت لتتعرف على بعض الميزات المتقدمة!” أيضًا. لقد أكملوا الدليل التعليمي بالفعل، لكنهم لا يزالون يتلقون الرسالة، وقد وصل عدد مرات إرسالها إلى 12 مرة على الأقل حتى الآن. لقد حاولوا إخبار discobot بتجاوز الرسالة، لكن ذلك لم يُحدث أي فرق. هل لديكم أي أفكار؟ وهل توجد طريقة للتحقق مما إذا كان هناك خلل في sidekiq؟

هل تستخدم أحدث إصدار من Discourse؟

نعم، على الإصدار 2.7.0.beta1. لقد تحققت أيضًا، ويبدو أن المشكلة لم تبدأ عند التحديث، بل بعد أسبوع تقريبًا.