pulumi down

sometimes takes more time than usual, for example 10 to 20 minutes for very small task, how can I find the reason ( how can I see more event details )

You can increase the verbosity:

--verbose 9

(or

-v=9

) should get you everything. For timeout issues, you won't see too much. And for big waits in the provider (e.g. deleted Route53 records), you'll have to infer a lot. I find that running the problematic command interactively and watching which resources take the longest to change can help diagnose things.

Thank you