• panostz

    (@panostz)


    Dear Support,

    Users constantly lose their discord role that it was assigned by the role mapping and we have to manually trigger the “Run API” in order to resign them the role.

Viewing 15 replies - 1 through 15 (of 20 total)
  • hey, on what events the members do loose roles ?

    Thread Starter panostz

    (@panostz)

    Its happening out of the blue.

    Thread Starter panostz

    (@panostz)

    It’s been 1 week and 2 days… Any update?

    Hey @panostz Sorry for staying silent.

    The issue keep happening with you?

    Could you please let us know what addon you are using along with PMPro.

    Also how many members you do have in your server?

    The role management depens upon site traffic as well.

    Thread Starter panostz

    (@panostz)

    Yeah I still have that. I have 120 users now but this is happening even when I had 30.

    Thread Starter panostz

    (@panostz)

    @ravisoniets Any news ?

    Thread Starter panostz

    (@panostz)

    @ravisoniets @vanbom The issue is still happening. Only today 5 people lost their discord role and I had to manually go to their user details and “RUN API”. We have to figure out why this is happening ASAP cause we are loosing clients. Please respond with a solution or the cause of this.

    FYI @strangerstudios @sunnysoni @expresstechsoftware

    • This reply was modified 3 months ago by panostz.
    • This reply was modified 3 months ago by panostz.
    Thread Starter panostz

    (@panostz)

    @ravisoniets@vanbom?The issue is still happening. Only today 5 people lost their discord role and I had to manually go to their user details and “RUN API”. We have to figure out why this is happening ASAP cause we are loosing clients. Please respond with a solution or the cause of this.

    Can you let me know also which is the cronjob that is doing that check so I can increase the interval?

    Please assist don’t leave the tickets without updates

    FYI?@strangerstudios @sunnysoni @expresstechsoftware

    ravisoniets

    (@ravisoniets)

    @panostz Thanks fpr staying on top of me.

    We need exact events at your membership setup where the members lose their roles, in our current testing rounds we found no such occurrences.

    I suggest updating following settings:

    Under Advanced settings tab of plugin

    Set Set job queue concurrency : 1

    set Set job queue batch size : 1

    Wait for few users event like new connection, payment failed, expire, and cancel to happen and then verify their roles.

    I suggest running “RUN API” once for all users to put them all on same page.

    Thread Starter panostz

    (@panostz)

    @ravisoniets Please let me know whats needed from my side and I can provide you the info.
    please find the links with some screen shots:

    Advanced Configuration: https://ibb.co/wLm1P9T

    Mapping: https://ibb.co/Q9KDknj

    The issue is happening out of the blue and I can confirm that. I was in call with a customer and without doing anything we been just talking, he lost his role. It works only if he go to the website and connect with discord or if I run the “RUN API”. once he done that he gets again a message from the bot to welcome him ( which should not happen since he is already a member with premium access ).

    It looks like it is loosing the connection with discord which is so wierd and very frustrating for our users. We already lost some of them and we cannot have this.

    (Note: Is it possible that this is happening because 2 website roles are matched to 1 discord role? Check mapping screenshot above )

    (Note2: About the Advanced configuration thats exactly what I had. I mentioned it also as resolution to another ticket because the users were not taking their role instantly after purchase of premium role. the issue was that it was initially configured to send batches of 7. after adding the values to 1 it was instant for all of them)

    Please assist.

    • This reply was modified 3 months ago by panostz.
    ravisoniets

    (@ravisoniets)

    Hey @panostz We need time to produce the env.

    Thread Starter panostz

    (@panostz)

    @ravisoniets@vanbom?@strangerstudios@sunnysoni@expresstechsoftware

    Hello, 2 weeks have passed. Any update?

    Regards,
    Panos

    Thread Starter panostz

    (@panostz)

    @ravisoniets@vanbom?@strangerstudios@sunnysoni@expresstechsoftware

    2 and a half month has passed and still I got no answer.
    EVERY DAY 3-5 people losing their access their discord role and I have to RUN API in order to go to them again.

    Can you please give me a solution on that or not? Thats your main product guys and is not working as expected.

    hey,

    Under role mapping tab

    make sure

    allow non-members is check

    then perform some tests

    Thread Starter panostz

    (@panostz)

    Hey @ravisoniets,

    I am not sure why you are repeating about this option and what that has to do with my MEMEBERS losing their discord role.

    This option ” allow non-members” is set to YES from the beginning. Also there are NO TESTS to be performed.

    I will say again the issue: Everyday i have users, that have an active membership and its roled mapped to discord role, loosing their discord role and I have to be 24/7 on top to RUN API and give them back their role.

    I see at least 5 tickets from other users that all have the same issue ” Users loosing their Discord Role” and you are replying the same “Check allow non-members”.

    If you cant give me a solution, can you please explain

    1) Why is this happening?
    2) What cronjob is revoking their roles?
    3) Is there a session or something that if users dont login to website they lose their role?
    4) What is the cronjob that checks all user ( like RUN-API for all users tho ) so I could manually run it or send me how I can put an interval to run this job every 15 minutes or so just to mitigate the issue

    • This reply was modified 1 month, 3 weeks ago by panostz.
Viewing 15 replies - 1 through 15 (of 20 total)
  • You must be logged in to reply to this topic.