🐛 Bug Report: Cannot GET /api/v1/organizations/settings

[sonic-sw]

📜 Description

Dear Novu Team,

while self-hosting novu, sending of emails is failing via the step component.
In the step component the preview is not working too, showing an issue with Cannot GET /api/v1/organizations/settings

Novu version 2.3

👟 Reproduction steps

1. Open Workflow with an email step
2. edit email step component
3. press on preview

or

1. Trigger worflow with step component
2. Sent Workflow
3. Mail step is failing

👍 Expected behavior

Ability to configure Organization settings with calls to the API endpoint

👎 Actual Behavior with Screenshots

Novu version

Novu Self-Hosted 2.3

npm version

No response

node version

No response

📃 Provide any additional context for the Bug.

No response

👀 Have you spent some time to check if this bug has been raised before?

• I checked and didn't find a similar issue

🏢 Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines

Are you willing to submit PR?

None

[linear]

NV-6435 🐛 Bug Report: Cannot GET /api/v1/organizations/settings

[ChmaraX]

Hi, thanks for the report.
The issue with the GET /api/v1/organizations/settings call in self-hosted environments has been fixed here: #8916 . It will be included in the next self-hosted release.

However, this doesn’t appear to be the cause of the preview failure or step/workflow errors you’re seeing. Could you share:

• The email content you’re using
• Any errors returned from the /api/v2/workflows/:workflow/step/:step/preview endpoint
• Relevant API error logs

This will help us determine whether the issue is related to your email content or something else.

[sonic-sw]

Dear @ChmaraX,
thank you for the update.

For the preview API Calls requested, I see the following in dev tools:

Request URL: https://notifications.XXX.com/api/v2/workflows/applicant-updates_wf_g4kikWZvm463TeMO/step/email-pending_st_g4llnneH1zjquhuP/preview
Request Method: POST
Status Code: 201

Response:
{
"data": {
"result": {
"preview": {},
"type": "email"
},
"previewPayloadExample": {
"payload": {
"onlineApplicationId": "onlineApplicationId",
"status": "status",
"value": {
"fullName": "fullName"
}
},
"subscriber": {
"subscriberId": "123456",
"firstName": "John",
"lastName": "Doe",
"email": "user@example.com",
"phone": "+1234567890",
"avatar": "https://example.com/avatar.png",
"locale": "en-US",
"data": {}
},
"steps": {}
},
"schema": null
}
}

[ChmaraX]

Hi @sonic-sw,

I tried spinning up a fresh Docker setup, but I couldn’t reproduce the issue. The preview endpoint response doesn’t seem to indicate any errors, it might be something in your email content.

Could you please:

• Check the API service logs for any errors around the time this happens.
• Try creating a new workflow with just a simple email step, then gradually add more content until the issue appears.
• If possible, share a minimal reproducible example (workflow configuration, email content, and any relevant logs) so we can investigate more effectively.

Without a reproducible case, it’s tricky to pinpoint the root cause.

I’ll close this issue as it’s covered by #8916.
If you’re still encountering problems - please open a new issue with a minimal reproducible example, detailed steps, and any relevant logs. This will help us determine whether it’s a separate bug and investigate it more effectively.