Skip to content

fix(task-manager): Updated Scheduler logic

Pankaj Kandpal requested to merge fix/task-notification-scheduler-errors into main

Currently, we are passing ctx as an empty JSON object in the scheduler code to send emails. The mutation parses the input as JSON if context is not null, with ctx as JSON object, input is being parsed as string, and throws an unexpected token error.

For the fix, I have checked the type of input, omit the parsing if its already a string. Also, setting ctx value in the mutation call to null if mails are triggered via scheduler. This would fix the email delivery issues with the scheduler, while the midnight time inconsistency is being addressed in !770 (merged)

Merge request reports