Skip to content

Subscriptions not firing #488

Closed
Closed

Description

@vsoch

I'm noticing that my subscriptions aren't firing beyond the first job returned, and I'm trying to figure out why. I read that they only fire for the specific client they are submit with, and I don't think that's my problem because I only have one. Are there specific things I can look into? The only issue I noticed is that when I left it running for a few hours and came back, the context seemed to have timed out, and I was getting errors from here about not being able to elect a new leader.

But the question is irrespective to that issue - I think it should be the case that I get a notification for each worker. I can see them running and complete, but only the first notifies. I'll keep trying things and thinking, and thank you in advance for the help!

Activity

  1. vsoch commented on Jul 31, 2024

    @vsoch
    Author

    Ah - I think I need a way to keep firing the waitForJob function. In the example https://github.com/riverqueue/river/blob/master/example_subscription_test.go we just need to wait for one job each, and I think that's what I might have missed (or at least this is my current hypothesis)!

  2. locked and limited conversation to collaborators on Jul 31, 2024
  3. converted this issue into a discussion #490 on Jul 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions