Reference: Advanced Workflows Best Practices and Limits

We recommend that you create a to-do task as the final task in your workflow to mark the workflow as completed, and assign the task to an administrator. This final task gives that administrator full control to review and finalize the workflow.

We recommend that you check with other administrators before you launch a workflow to ensure that no other workflows exist for the same version, sheets scope, and levels. If multiple workflows launch for the same coordinates across hubs, the assignees for both workflows might override each other’s actions on the data. Example: A user from one workflow completes their task to edit sheet data, but afterwards, a user from another workflow tries to edit that same sheet data.

We recommend that you only launch workflows from shared hubs.

To enable workflows administrators to manage your workflow definition and workflow capacity, share all hubs with workflows with those administrators. Users with the

Manage Workflows

permission can only manage workflows on hubs that are shared with them. If you reach your maximum capacity, administrators with access to only some of the hubs can’t see the workflow definitions and workflows on the other hubs.

We don’t currently support:

User-assigned sheets as task destinations.
Attachments in tasks.
Workflows in actuals versions.

If you require support for these features that we don’t currently support, contact us so that we can consider it in our future roadmap.

These are the maximum amounts allowed for these configurable workflows objects:

15 maximum workflow definitions per instance. These workflow definitions can exist across different hubs.
100 maximum workflows in your tenant. These workflows can exist across different workflow definitions and hubs.
10 maximum workflows per version.
5 maximum approval tasks connected to 1 submit task.
20 maximum tasks in 1 workflow definition.