Response from queue

Question

I create a simple queue-job system with using BullQueue in TypeScript and NestJS like below:

    async addToQueue(): Promise<void> {
        try {
            await this.reportQueue.add('generate_report', {
                //some data
            })
            this.logger.log(`Added to queue.`)
        } catch (error) {
            this.logger.error(`Not added to Queue.`);
        }
    }


    @Process('generate_report')
    async generateReport(job: Job<{options: ReportFilterDto, context: CustomContext, reportType: Type, worktime?: WorktimeDto}>): Promise<any> {
        try {
            //some working code
        } catch (error) {
            //
        }
    }

    @OnQueueActive()
    async onActive(job: Job): Promise<void> {
        //
    }

    @OnQueueCompleted()
    async onCompleted(job: Job): Promise<void> {
        //
    }

    @OnQueueWaiting()
    async onWaiting(job: Job): Promise<void> {
        //
    }

    @OnQueueFailed()
    onError(job: Job<any>, error: BadRequestException): void {
        //
    }

i run my function addToQueue() from my controller where i provide a parameters, buuuuuut it is possible to return any response to the client from the queue about sucessfull or failed job? If it is possible can someone show how to do it?

thanks for any help

.////////////////////////.

Answer 1

Immediately, there isn't really any way. A queue is there so you can run asynchronous tasks without blocking your main thread or holding up your server in any way. If you were to want to return the result, depending on the job the queue is running, you could be waiting for a few seconds to a few days (a bit of an exaggeration, but it gets the point across). What you could do instead is one of two things (at least that come immediately to mind)

1. return an Id that you create that relates back to this job. When the job finishes, save the result with that Id to the database. Then, the user can request the status at any time.

2. Take note of the user who sent in the request, and send an email to that user once the job completes. This will require more integrations, but can get more accurate results over "Ping every so often and we'll tell you if it's done".

Both approaches are valid, and you could even make a combination of the two (probably the best of both worlds so you can save the results and alert the user when it's done).