Closed aleksa-krolls closed 1 year ago
@mtuchi new UNICEF issue in prod - can you please take a look ASAP either today or tomorrow morning? cc @daissatou2 please see email to the client, and help with testing once Mtuchi has fixed this.
@aleksa-krolls here is the fix #79, i have tested it on staging to be safe but it seems like the credentials might not exist anymore See run log here
Describe the bug
Thanks to issue #65 , the custom error handling is working well in Job1 of this flow. However, once this custom error is thrown (see example run)... then the next Job2 in the flow should send a "delivery failed" notification to Progres.
However, if you look at this next run no alert is being sent, even though Job1 failed.
I expect this error to be thrown... maybe in issue #65 we changed the logging in a way that broke how this Job2 works? Maybe the console.logs in Job1 need to contain the full string
Service value shared
in order for this job to behave as expected? https://github.com/OpenFn/primero-progres/blob/master/jobs/PROD/f1-3.sendErrorToDTP.js#L19-L23To Reproduce
expression.js
Branch off of
main
and submit a PR when ready to testJob1 to test with using
language-primero@2.3.4
: https://github.com/OpenFn/primero-progres/blob/master/jobs/PROD/f1-1.sendReferralsToPrimero.jsJob2 to get working using
language-http@4.0.0
: https://github.com/OpenFn/primero-progres/blob/master/jobs/PROD/f1-3.sendErrorToDTP.jsstate.json
Job1:
Job2 → Please comment out all operations so to not actually try sending this job to DTP… just try to resolve the console.log() issue.
Expected behavior
After we job1 fails, we should send an error alert to DTP in job2.
Toggl
UNICEF Primero-Progres Support [2022-24]