Change of arguments in Invoke Workflow should give error at compile time

When I change argument name or add new argument to child workflow resulting in only orange highlight on argument count.

If I missed to check the reference of the workflow where it’s invoked, this gets smoothly deployed to higher environment and fails at runtime.

Can we have error debugging so this will not get missed.

Any workaround anyone using to avoid this?

Thanks,
Ashok :slight_smile:

Hi @ashokkarale

After we completed the recent Invoke Workflow File redesign, we are now considering a workflow analyzer rule to let you catch all misconfigured instances:

Thank you for reinforcing the need for this :slight_smile:

That’s wonderful news @loginerror. Thank you for the update. Looking forward for the update soon :star_struck: