Submit your inspiring success story or innovative use case to the 2022 Dataiku Frontrunner Awards! ENTER YOUR SUBMISSION

Debugging/Versioning Applications as a Recipe

yashpuranik
Level 3
Level 3
Debugging/Versioning Applications as a Recipe

Hi,

I am looking into packaging a part of a flow as a recipe to be used across multiple projects (https://doc.dataiku.com/dss/latest/applications/application-as-recipe.html#sharing-an-application-as...). I have a couple of questions:

1. It appears that any changes made in the original project get transmitted to all projects where the recipe is used. Is it possible to create versions and tracking them?

2. Suppose the application-as-a-recipe fails. The error message returned is fairly unhelpful (see attached). This failure happened due to a division by 0 error in a Python recipe. What is the easiest way to debug an application-as-a-recipe when there are failures? (Preferably, this does not involve running the original flow with the inputs that triggers errors).

yashpuranik
0 Kudos
2 Replies
yashpuranik
Level 3
Level 3
Author

As a follow up,  checking keep instance (https://community.dataiku.com/t5/Using-Dataiku/Applications-as-recipes-and-logging/m-p/14441) works for debugging. It creates new projects in a folder called App Instances and names start with Execute

 

yashpuranik
0 Kudos
CoreyS
Community Manager
Community Manager

Thank you for sharing how you found the solution with the rest of the community @yashpuranik!

Looking for more resources to help you use Dataiku effectively and upskill your knowledge? Check out these great resources: Dataiku Academy | Documentation | Knowledge Base

A reply answered your question? Mark as ‘Accepted Solution’ to help others like you!
0 Kudos