Hi developers i am trying to work on queue in next.js 13 with a custom api. This is how far I got... the api is working the connection to redis is working but the middle is not working im trying…
This works for local redis-server BullModule.forRoot({ redis: { host: "localhost", port: 6379, db: 0, password: "" } }) But if I use the DataStore Credentials on Heroku Redis, the bull board does not load and Heroku Logs gives an H12…
I am using BullModule in nest.js. when I connect to a local redis it works: const REDIS = { host: 'localhost', }; @Module({ imports: [ TaskTypesModule, TasksModule, ScheduleModule.forRoot(), BullModule.forRoot({ // @ts-ignore redis: REDIS, }), ], controllers: [AppController], providers: [AppService, PrismaService],…
I am using npm bull to add my queue job to handle about sending mail for my project. It runs no problems for a long time, but recently, it shows this error: Error while handling task collect-metrics: Reached the max…
Problem When I upgraded from the Heroku Redis Hobby plan to the Heroku Redis Premium 0 plan, Heroku kept crashing with an H10 error.
I have an application that makes API calls to another system, and it queues these API calls in a queue using Bull and Redis. However, occasionally it gets bogged down with lots of API calls, or something stops working properly,…
i got error when i queue with bull library in node js, the error is like this : Error: read ECONNRESET at TCP.onStreamRead - - errno: -104, - - code: 'ECONNRESET', - - syscall: 'read' - - } and MaxRetriesPerRequestError:…
Basically, each of the clients ---that have a clientId associated with them--- can push messages and it is important that a second message from the same client isn't processed until the first one is finished processing (Even though the client…