You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because the FX flow does not include such a call, the FXP implementations will likely not include such handler and it will not be included in the participantEndpoint table in the DB. The result is Invalid template error, which breaks the handling of the FX_RESERVE message:
2024-06-26T14:00:29.648Z - error: Consumer::onError()[topics='topic-notification-event'] - FSPIOPError: Error processing notification message
at createFSPIOPError (/opt/app/node_modules/@mojaloop/central-services-error-handling/src/factory.js:198:12)
at Object.createInternalServerFSPIOPError (/opt/app/node_modules/@mojaloop/central-services-error-handling/src/factory.js:314:10)
at /opt/app/src/handlers/notification/index.js:162:52
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async consumeMessage (/opt/app/src/handlers/notification/index.js:161:21)
FSPIOPError: Invalid template! Template should be a "string" but "undefined" was given as the first argument for mustache#render(template, view, partials)
at createFSPIOPError (/opt/app/node_modules/@mojaloop/central-services-error-handling/src/factory.js:198:12)
at Object.reformatFSPIOPError (/opt/app/node_modules/@mojaloop/central-services-error-handling/src/factory.js:333:12)
at exports.getEndpoint (/opt/app/node_modules/@mojaloop/central-services-shared/src/util/endpoints.js:175:32)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Object.getEndpoint (/opt/app/src/domain/participant/index.js:76:17)
at async processMessage (/opt/app/src/handlers/notification/index.js:381:31)
at async consumeMessage (/opt/app/src/handlers/notification/index.js:161:21)
TypeError: Invalid template! Template should be a "string" but "undefined" was given as the first argument for mustache#render(template, view, partials)
at Object.render (/opt/app/node_modules/mustache/mustache.js:753:13)
at exports.getEndpoint (/opt/app/node_modules/@mojaloop/central-services-shared/src/util/endpoints.js:171:21)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Object.getEndpoint (/opt/app/src/domain/participant/index.js:76:17)
at async processMessage (/opt/app/src/handlers/notification/index.js:381:31)
at async consumeMessage (/opt/app/src/handlers/notification/index.js:161:21))
The text was updated successfully, but these errors were encountered:
There is an associated todo in the notification handler.
Because the FX flow does not include such a call, the FXP implementations will likely not include such handler and it will not be included in the
participantEndpoint
table in the DB. The result isInvalid template
error, which breaks the handling of the FX_RESERVE message:The text was updated successfully, but these errors were encountered: