Quick question: if your existing code already has @retry decorator, and logging module and so on... what does prefect do with them? is it using them as some sort of internal config for its own (retry, logging ...) tools?

Hi @loz! I've heard of people creating their own decorators and using them in their Prefect scripts. I do believe they'll be respected if you'd like to use them in lieu of the Prefect decorator args (retries, log_prints, timeout, etc.). We typically encourage people to use the default Prefect decorators (@flow and @task) and available args, just to avoid any unexpected behavior with the orchestrator.