If a child or a downstream asset is created after running a workflow, tags for that asset will be propagated automatically. When a new asset is registered, tag propagation is automatically triggered in the metastore and runs as a background task.
For example, if a workflow adds an additional column to a table, a new background task for adding tags will be created in the metastore. This new task will be executed when all the previous tasks have been completed in the queue. The speed with which these tasks will be completed depends on the number of pending tasks as well as the volume of tags to be added or removed. The same process also applies to tag deletion and updating tags through playbooks.
