I do not understand the workflows

[SebastianStehle]

Hi,

I am trying out novu. More of interest because I built something like this myself (https://github.com/notifo-io/notifo). But the workflow editor confuses me:

Here is an image for reference:

1. Why are the filters not special nodes?
2. Why are notifications sent sequentially and not parallel?
3. Is the SMS sent when the App message fails to be sent?
4. Is there a retry for SMS and app and how does it impact the order?
5. Is digest applied to all consecutive messages or just the next one?
6. The workflow does not match to the graphics on the start page.

It feels more like a graphics representation for something that is actually not a real workflow.

Something about UX:

1. The nodes should show a summary, e.g. the digest properties or the filter, so that I can understand the workflow without having a look to the details.
2. The validation "dot" on the left is only updated when I press "Update"
3. Before I press "Update" the validation shows "Something is missing here". After Update the correct message is shown.
4. It is annoying that I have to close properties all the time.
5. The four icons on the left are confusing, because they have nothing to do with the workflow. It is more like a tab control.
6. The validation message like "Subject is missing" is not shown on the properties page.

[scopsy]

Hi @SebastianStehle thank you so much for the feedback! Will address each bulley below:

• Why are the filters not special nodes?
  This is because we won't to allow filter particular action and not all the downstream actions, in the future a filter node will be added to support this functionality
• Why are notifications sent sequentially and not parallel?
  This is on our roadmap to allow parallel workflow tree execution. Not available today.
• Is the SMS sent when the App message fails to be sent?
  From this version this could be specified in the configuration, by default it will execute even if one node failed.
• Is there a retry for SMS and app and how does it impact the order?
  For now we don't have a retry policy, however we plan to add this on our roadmap
• Is digest applied to all consecutive messages or just the next one?
  Applied to all consecutive messages
  The workflow does not match to the graphics on the start page.
  This is definitely something we are working on right now to allow filters based on user online activity and parallel execution. Will consider revisiting the flow there to better match current flow, but hopefully will be able to match functionality in the next couple of releases
  It feels more like a graphics representation for something that is actually not a real workflow.

Something about UX:

• The nodes should show a summary, e.g. the digest properties or the filter, so that I can understand the workflow without having a look to the details.
  Very good point! Will create an issue for this
• The validation "dot" on the left is only updated when I press "Update", Before I press "Update" the validation shows "Something is missing here". After Update the correct message is shown.
• It is annoying that I have to close properties all the time.
  Thanks for noticing this, will look for a better solution and create an issue for it.
• The four icons on the left are confusing because they have nothing to do with the workflow. It is more like a tab control.
  We have some concerns regarding the current navigation pattern on the workflow editor, considering a few other alternatives in the next couple of weeks to try find a better way to handle navigation between those tabs
• The validation message like "Subject is missing" is not shown on the properties page.
  Seems like a bug 🙏

Thank you so much for time writing this and take a look at Novu, I will create issues internally and in general, would love to jump on a call to hear more about your journey at notifio.

[SebastianStehle]

Thanks for your reply. If you want to have a call, just use my calendly: https://calendly.com/squidex-meeting/30min?month=2022-12

[SebastianStehle]

Just one more question:

1. What happens when the server is stopped while a workflow is executed?

[scopsy]

Scheduled a call 🎉

Each workflow step is scheduled using a queue mechanism and will be executed using a queue listener once a new machine is up. Same goes for load balancing large queues.

[SebastianStehle]

Great. This does not answer my question. If I have two actions, like SMS and Mobile and the server is restarted after SMS, what happens?

1. The workflow is already removed from the queue and Mobile will never be sent.
2. The state of the workflow is persisted and the workflow continues with the mobile step.
3. The workflow is not removed from the queue yet, the SMS will be sent again and after that Mobile Push is sent.

[scopsy]

Option no.2 will happen. Only the not processed yet steps will be executed.