Cloned flow best practices and troubleshooting

Cloning a flow is a useful way to reuse automation logic, but cloned flows are not always ready to use. Connections, references, and logic may not carry over correctly or require adjustments. 

Ziflow recommends the following when cloning flows to get the best results:

1. Clone the flow

2. Reassign or confirm all connections

3. Review Zibot order and references

4. Validate logic and conditions

5. Test with real data

6. Activate only after successful validation

Reconfigure all connections

A common issue when cloning a flow is that the cloned flow may have a different owner than the original. When this happens, any connections set up by the original owner may no longer work.

After cloning, reconfigure all connections to ensure they are valid for the new owner.

To avoid disruptions when ownership changes, consider creating and using a shared Admin account to create and manage automation flows. This helps ensure flows continue to function even if individual users change roles or leave the organization.

After cloning, review every Zibot that uses an integration.

• Select the correct connection for the new owner

Validate all Zibot references

Check every reference to $.zibot[X].

• Confirm the index points to the correct step

• Update references if any Zibots were added, removed, or reordered

Keep logic consistent

Make sure the flow uses the correct objects and endpoints throughout.

• Use task-related steps only with tasks

• Use folder/project steps only with folders

Avoid mixing them within the same logic path.

Review and simplify logic

Cloning can amplify complexity.

• Remove unnecessary steps

• Avoid layering fixes on top of existing logic

• Refactor where needed before activating

Double-check webhook configurations

If the flow uses webhooks:

• Verify authentication (headers, tokens)

• Confirm endpoints are correct

• Ensure responses match expected structure

Webhook steps are more sensitive to configuration errors.

Test 

Run the flow as soon as it is cloned and updated.

Validate:

• Successful execution paths

• Failure scenarios (for example, no results found)

• Conditional branches

Do not assume the cloned flow behaves like the original.