Please add the workflow graphical view in Office365..this must be useful for the enduser...

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.

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

I am in the middle of developing a workflow, and when the workflow hits an "O365" action, it freezes for several minutes. HUGE performance issue!!

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.

Currently, workflow variables are displayed in the order they are created, which is inflexible.

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.

The behaviour of the Start Workflow action is to suspend the originating workflow if an instance of the called workflow already exists for the list item.

Proposed is an enhancement to either:
1. allow the Start Workflow action to be configured such that the originating workflow is allowed to continue
or
2. introduce a 'Check Workflow' action that returns a value to indicate if if an instance of a workflow exists for a list item

Currently available on premises.

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.

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.

Since we sometimes can not rely fully on the Microsoft REST service endpoints (for example for SharePoint Online) especially when looping those calls in a workflow, it would be very nice if Nintex Workflow added some automatic polling (Do-Until) to retry web services calls if they fail with some sort of 500 error. The same functionality I was aiming for will be introduced into Azure Logic Apps as can be viewed here: https://www.youtube.com/watch?v=J7PyjKkkNu0. This should enhance the stability of our Workflow solutions

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

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.

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

Find string in substring toggle case sensitivity.

When using this action there's not function to toggle case sensitivity.

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?

Send Document to Repository Action does not work. I have tried moving the document in the same site with no luck. I just get this error "Unable to find document to repository." what does this mean and why am I getting it. - Content Organizer is turned on.

I have three workflows for one list, all are set not to start when an item is created in the list. Issue is that all three workflows start automatically no matter what setting is selected.

Having options to start workflow when item created, updated, or manual are useless if they all run automatically.

I have two Nintex workflow in separate SharePoint list (workflow1 in List1 and workflow2 in list2). workflow1 will update a column from ‘No’ to ‘Yes’ in list2, in this case wokflow2 should trigger because ‘Start when items are modified’ is enabled in workflow2. However it not happening. Any issue with settings?