I'm curious about the CHAINED_EXECUTION_NODE_LIMIT property in custom.proper

We've bumped up against the 100 limit before as well, but always found ways to reduce the number of nodes on the chain. Determine what causes race conditions, and which nodes might be able to split off into a parallel asynchronous sub-process call. Many script tasks can be combined, if they don't have inter-dependencies. Worst case, you have to add a task partway through the chain with some instructional text that the user clicks past, but hopefully that is avoided. You might also consider whether this should be a wizard, or if they should receive the task on the dashboard/tasks list when it's available, or as a related action.

We've bumped up against the 100 limit before as well, but always found ways to reduce the number of nodes on the chain. Determine what causes race conditions, and which nodes might be able to split off into a parallel asynchronous sub-process call. Many script tasks can be combined, if they don't have inter-dependencies. Worst case, you have to add a task partway through the chain with some instructional text that the user clicks past, but hopefully that is avoided. You might also consider whether this should be a wizard, or if they should receive the task on the dashboard/tasks list when it's available, or as a related action.