Empty profile of workfile template set it should stop silently instead of raising exception

[moonyuet]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior:

As we have the callback which executes to create first workfile from workfile template in the hosts, the integration would error without try, exception with TemplateProfileNotFound.
See e.g.: https://github.com/ynput/ayon-nuke/blob/4d6baa170d123e6df4167e4d0ecb4f6e95a77439/client/ayon_nuke/api/lib.py#L2571-L2576
https://github.com/ynput/ayon-houdini/blob/b1ac1461d3829dad49ae9af1bff48db7d6e2dd20/client/ayon_houdini/api/lib.py#L1569-L1573

The root cause of the lines:

ayon-core/client/ayon_core/pipeline/workfile/workfile_template_builder.py

Lines 867 to 870 in b737a51

	raise TemplateProfileNotFound((
	"No matching profile found for task '{}' of type '{}' "
	"with host '{}'"
	).format(task_name, task_type, host_name))

Expected Behavior:

Ayon should stop sliently the workfile templated building workflow when empty profile found.

Version

1.9.7

What platform you are running on?

Windows

Steps To Reproduce:

Use Blender as example

1. Build addon in Blender with ynput/ayon-blender@69a8849
2. Make sure ayon+settings://blender/templated_workfile_build with no profiles
3. Launch Blender

Are there any labels you wish to add?

• I have added the relevant labels to the bug report.

Relevant log output:

Additional context:

No response

[moonyuet]

@BigRoy @iLLiCiTiT any thoughts on this?

[iLLiCiTiT]

My thoughs are that you're poking snake with bare hands 🙂(Joke) .

I do believe the error is correct, having in mind the current implementation of the workfile builder. It really does deserve more things to refactor before that. From all the things the workfile builder has, this is the least problematic part, from my point of view. The idea was that you should show a message to the user if something is wrong, for example when nothing happens because the settings are not filled. That can be achieved in much better way, but not with the current implementation.

[BigRoy]

Let's do that. There's some more pet peeves on this so let's do that clean up because I believe @moonyuet has it on her backlog to improve some other things for it. So I guess, time to schedule that conversation!