The The syntax is simply While info statements have no effect on the workflow’s functional outcome, best practice is to remove or comment them out before deploying an application to production users. Leaving many info statements active in a production script generates unnecessary log volume and can slightly affect script execution performance in high-frequency workflows.<\/p>\n","protected":false},"excerpt":{"rendered":" The Deluge info statement outputs a value to the script execution log during testing, helping developers debug Deluge code by inspecting variable states.<\/p>\n","protected":false},"template":"","meta":{"seo_title":"Deluge info Statement | Zoho Glossary | Aaxonix","seo_description":"The Deluge info statement outputs a value to the script execution log during testing, helping developers debug Deluge code by inspecting variable states.","seo_keyword":"Zoho Deluge info statement","seo_faqs":"","term_type":"","glossary_related":"","glossary_links":""},"glossary_category":[1258],"class_list":["post-5142","glossary","type-glossary","status-publish","hentry","glossary_category-zoho-creator"],"_links":{"self":[{"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/glossary\/5142","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/glossary"}],"about":[{"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/types\/glossary"}],"wp:attachment":[{"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/media?parent=5142"}],"wp:term":[{"taxonomy":"glossary_category","embeddable":true,"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/glossary_category?post=5142"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}info<\/code> statement in Deluge is a debugging tool that writes a value or message to the execution log when a script runs. Developers use it the way they would use console.log<\/code> in JavaScript or print<\/code> in Python: to inspect variable values, confirm that conditional branches executed, and trace data flow through a script without interrupting the user experience.<\/p>\nHow to Use info<\/h2>\n
info expression;<\/code> where expression can be a variable, a field value, a string literal, or a computed value. For example, info input.Email;<\/code> will write the submitted email address to the log. Multiple info statements can be placed at key points in a script to create a step-by-step trace of execution. The output appears in Creator’s script execution log, accessible from the workflow editor during testing.<\/p>\nRemoving info Statements in Production<\/h2>\n