deliver_later with ActionMailer not sending mail in production












0















deliver_later with ActionMailer not sending mail in production.



I am using




rails 5.2.0 and
delayed_job_active_record 4.1.3




I have tried deliver and deliver_now in production and the email is getting sent successfully. As soon as I change to deliver_later, the job gets queued but it's never executed.



if user.notify_new_event?
EventMailer.notify_created(user.id, id).deliver_later
end


deliver_later with ActionMailer should behave like deliver_later with ActiveJob. But some how the deliver_later with ActionMailer is not working.










share|improve this question




















  • 1





    Not a whole lot of detail, but possibly related to this question... ? Let us know.

    – gravitymixes
    Jan 2 at 13:32











  • Not exactly. I have started the delayed job server in the production using RAILS_ENV=production bin/delayed_job start

    – Tashi Dendup
    Jan 2 at 13:39











  • My question is basically on gem delayed_job_active_record. Please checkout this documentation github.com/collectiveidea/delayed_job

    – Tashi Dendup
    Jan 2 at 14:19











  • OK, are jobs showing up in the database? What's in your .log file? As my first comment mentioned, we don't have a lot of detail to help you without knowing what you've validated first.

    – gravitymixes
    Jan 2 at 14:32











  • Jobs are correctly getting inserted in the database. But the job execution never starts even if the job server is up. This is my delayed job log. I, [2019-01-02T13:26:20.532345 #17000] INFO -- : 2019-01-02T13:26:20+0000: [Worker(delayed_job host:clapp pid:17000)] Starting job worker

    – Tashi Dendup
    Jan 3 at 8:12
















0















deliver_later with ActionMailer not sending mail in production.



I am using




rails 5.2.0 and
delayed_job_active_record 4.1.3




I have tried deliver and deliver_now in production and the email is getting sent successfully. As soon as I change to deliver_later, the job gets queued but it's never executed.



if user.notify_new_event?
EventMailer.notify_created(user.id, id).deliver_later
end


deliver_later with ActionMailer should behave like deliver_later with ActiveJob. But some how the deliver_later with ActionMailer is not working.










share|improve this question




















  • 1





    Not a whole lot of detail, but possibly related to this question... ? Let us know.

    – gravitymixes
    Jan 2 at 13:32











  • Not exactly. I have started the delayed job server in the production using RAILS_ENV=production bin/delayed_job start

    – Tashi Dendup
    Jan 2 at 13:39











  • My question is basically on gem delayed_job_active_record. Please checkout this documentation github.com/collectiveidea/delayed_job

    – Tashi Dendup
    Jan 2 at 14:19











  • OK, are jobs showing up in the database? What's in your .log file? As my first comment mentioned, we don't have a lot of detail to help you without knowing what you've validated first.

    – gravitymixes
    Jan 2 at 14:32











  • Jobs are correctly getting inserted in the database. But the job execution never starts even if the job server is up. This is my delayed job log. I, [2019-01-02T13:26:20.532345 #17000] INFO -- : 2019-01-02T13:26:20+0000: [Worker(delayed_job host:clapp pid:17000)] Starting job worker

    – Tashi Dendup
    Jan 3 at 8:12














0












0








0








deliver_later with ActionMailer not sending mail in production.



I am using




rails 5.2.0 and
delayed_job_active_record 4.1.3




I have tried deliver and deliver_now in production and the email is getting sent successfully. As soon as I change to deliver_later, the job gets queued but it's never executed.



if user.notify_new_event?
EventMailer.notify_created(user.id, id).deliver_later
end


deliver_later with ActionMailer should behave like deliver_later with ActiveJob. But some how the deliver_later with ActionMailer is not working.










share|improve this question
















deliver_later with ActionMailer not sending mail in production.



I am using




rails 5.2.0 and
delayed_job_active_record 4.1.3




I have tried deliver and deliver_now in production and the email is getting sent successfully. As soon as I change to deliver_later, the job gets queued but it's never executed.



if user.notify_new_event?
EventMailer.notify_created(user.id, id).deliver_later
end


deliver_later with ActionMailer should behave like deliver_later with ActiveJob. But some how the deliver_later with ActionMailer is not working.







ruby-on-rails-5 delayed-job






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 2 at 13:32







Tashi Dendup

















asked Jan 2 at 13:29









Tashi DendupTashi Dendup

217




217








  • 1





    Not a whole lot of detail, but possibly related to this question... ? Let us know.

    – gravitymixes
    Jan 2 at 13:32











  • Not exactly. I have started the delayed job server in the production using RAILS_ENV=production bin/delayed_job start

    – Tashi Dendup
    Jan 2 at 13:39











  • My question is basically on gem delayed_job_active_record. Please checkout this documentation github.com/collectiveidea/delayed_job

    – Tashi Dendup
    Jan 2 at 14:19











  • OK, are jobs showing up in the database? What's in your .log file? As my first comment mentioned, we don't have a lot of detail to help you without knowing what you've validated first.

    – gravitymixes
    Jan 2 at 14:32











  • Jobs are correctly getting inserted in the database. But the job execution never starts even if the job server is up. This is my delayed job log. I, [2019-01-02T13:26:20.532345 #17000] INFO -- : 2019-01-02T13:26:20+0000: [Worker(delayed_job host:clapp pid:17000)] Starting job worker

    – Tashi Dendup
    Jan 3 at 8:12














  • 1





    Not a whole lot of detail, but possibly related to this question... ? Let us know.

    – gravitymixes
    Jan 2 at 13:32











  • Not exactly. I have started the delayed job server in the production using RAILS_ENV=production bin/delayed_job start

    – Tashi Dendup
    Jan 2 at 13:39











  • My question is basically on gem delayed_job_active_record. Please checkout this documentation github.com/collectiveidea/delayed_job

    – Tashi Dendup
    Jan 2 at 14:19











  • OK, are jobs showing up in the database? What's in your .log file? As my first comment mentioned, we don't have a lot of detail to help you without knowing what you've validated first.

    – gravitymixes
    Jan 2 at 14:32











  • Jobs are correctly getting inserted in the database. But the job execution never starts even if the job server is up. This is my delayed job log. I, [2019-01-02T13:26:20.532345 #17000] INFO -- : 2019-01-02T13:26:20+0000: [Worker(delayed_job host:clapp pid:17000)] Starting job worker

    – Tashi Dendup
    Jan 3 at 8:12








1




1





Not a whole lot of detail, but possibly related to this question... ? Let us know.

– gravitymixes
Jan 2 at 13:32





Not a whole lot of detail, but possibly related to this question... ? Let us know.

– gravitymixes
Jan 2 at 13:32













Not exactly. I have started the delayed job server in the production using RAILS_ENV=production bin/delayed_job start

– Tashi Dendup
Jan 2 at 13:39





Not exactly. I have started the delayed job server in the production using RAILS_ENV=production bin/delayed_job start

– Tashi Dendup
Jan 2 at 13:39













My question is basically on gem delayed_job_active_record. Please checkout this documentation github.com/collectiveidea/delayed_job

– Tashi Dendup
Jan 2 at 14:19





My question is basically on gem delayed_job_active_record. Please checkout this documentation github.com/collectiveidea/delayed_job

– Tashi Dendup
Jan 2 at 14:19













OK, are jobs showing up in the database? What's in your .log file? As my first comment mentioned, we don't have a lot of detail to help you without knowing what you've validated first.

– gravitymixes
Jan 2 at 14:32





OK, are jobs showing up in the database? What's in your .log file? As my first comment mentioned, we don't have a lot of detail to help you without knowing what you've validated first.

– gravitymixes
Jan 2 at 14:32













Jobs are correctly getting inserted in the database. But the job execution never starts even if the job server is up. This is my delayed job log. I, [2019-01-02T13:26:20.532345 #17000] INFO -- : 2019-01-02T13:26:20+0000: [Worker(delayed_job host:clapp pid:17000)] Starting job worker

– Tashi Dendup
Jan 3 at 8:12





Jobs are correctly getting inserted in the database. But the job execution never starts even if the job server is up. This is my delayed job log. I, [2019-01-02T13:26:20.532345 #17000] INFO -- : 2019-01-02T13:26:20+0000: [Worker(delayed_job host:clapp pid:17000)] Starting job worker

– Tashi Dendup
Jan 3 at 8:12












1 Answer
1






active

oldest

votes


















0














It was not the problem with ActionMailer with DelayedJob. Rather the problem was with multi-tenant application. By default delayed_job was trying to execute job from the default tenant.






share|improve this answer























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54007256%2fdeliver-later-with-actionmailer-not-sending-mail-in-production%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    It was not the problem with ActionMailer with DelayedJob. Rather the problem was with multi-tenant application. By default delayed_job was trying to execute job from the default tenant.






    share|improve this answer




























      0














      It was not the problem with ActionMailer with DelayedJob. Rather the problem was with multi-tenant application. By default delayed_job was trying to execute job from the default tenant.






      share|improve this answer


























        0












        0








        0







        It was not the problem with ActionMailer with DelayedJob. Rather the problem was with multi-tenant application. By default delayed_job was trying to execute job from the default tenant.






        share|improve this answer













        It was not the problem with ActionMailer with DelayedJob. Rather the problem was with multi-tenant application. By default delayed_job was trying to execute job from the default tenant.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jan 31 at 7:29









        Tashi DendupTashi Dendup

        217




        217
































            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54007256%2fdeliver-later-with-actionmailer-not-sending-mail-in-production%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Monofisismo

            Angular Downloading a file using contenturl with Basic Authentication

            Olmecas