WHen you use Office 365 upload file, if the site does not exist the workflow gets suspended. Testing for the site and library existence is not trivil. Please add some error handling to this action so that it returns No if the site does not exist, or Nintex does not have access, rather than suspending the workflow.

Nintex O365 Workflow failure should monitor 'Terminated' workflows and send out alert when it happens. We have a few incidents caused by terminated workflows but we weren't aware of.

If the action, Office 365 Update Items cannot find the item you are looking for, the whole workflow fails, rather than simply updating 0 rows. You have a nice variable to return yes if rows are updated, but the workflow fails if no rows are updated.

External email errors when using text variable containing several emails separated by semicolon AND a space.

If the spaces are removed it works.

Setting business hours for initial emails and reminders.Looking for the Same configuration in Assign a task process Action in O365.

Setting a modified start condition in the workflow Settings does not trigger the workflow to start when the document library item is modified (a document set). The modified start condition compares the values of two fields on the document library item and should start the workflow if they are not equal. The two fields being compared are People fields with multiple selctions possible.

I can't do simple math operations on currency columns because they get treated like unparsable strings.

"$100" * 1.43 = Exception casting "$100" to type double.

Please provide a way to not have "$" as part of the value................

Need a way to test user credentials and connections. Workflow keeps indicating bad username format or password or something and I can't make sense of if it is the connection or the parameter to the query.

Currently our Site workflows have been firing an hour early due to Daylight Saving Time ending for this year. This is apparently not a bug for some reason, and should be considered such.

Right now I can't find any way to see the history of a component workflow called from another workflow. If possible it'd be great to have component workflows log to the caller's history.

As of now, any component workflows created in a Office 365 is visible to all users within the tenant. This will create confusion in scenarios where in the component workflow is required for a specific site collection and not to be visible for others.

A visibility flag might help a long way to target component workflows for specific site collections rather than entire O365 tenant

Currently if the rich text has a table element, the table has not rendered as it is on the result of Nintex document generation action

We are trying to figure out how to remove headers from emails from the workflow in SharePoint online. I see you have a KB article:

https://support.nintex.com/SharePoint/Workflow/Disabling_Header_and_Footer_in_Notification_Message

But that appears to only be for SharePoint on-prem. How do we disable them in SharePoint online?

I opened case number 00246103 and they suggested I post here. They are still researching. I would call this a feature request.

I added a comment to this idea: https://nintex.uservoice.com/forums/218291-3-nintex-workflow-for-office-365/suggestions/5740552-email-notifications-having-approve-reject-bu, but not sure if the comments are being monitored since it is marked as completed.

Based on my clients' feedback, the greatest need for button approval via email is from mobile devices. When I access the LazyApproval email from my iPhone, the actionable buttons are not there.

Side note: The actionable message buttons are available via my iPhone for Flow tasks.

A way to show the component workflow status of a component workflow in Nintex Workflow for Office 365

I have received some errors where I don't know what to do, because the error is not clear and I can't find anything in internet,
For example: EventAggregator. What is that? What does it mean? What should I do?

Currently an out of office email causes LazyApproval within O365 to send a second email saying that the response was not valid. LazyApproval should know that it's an out of office email like the system does on-prem.

Currently, Nintex for O-365 workflows are not able to parse the Date and Time from the following publishing fields - Scheduling Start Date/End Date. Any workflow email that includes these fields shall display incorrect time (due to time-zone difference between the Nintex App and the Site-Collection). We would need this to be corrected, as all the site-collections will not be in the same time-zone where the Nintex Apps are hosted.

Allow the option to skip an action if an error occurs while performing it. For example, if a user-defined emailed address is undeliverable for sending a notification, then allow the workflow to continue.

Currently available on premises.