You need something from the US team to move forward at 11 am, but they are not working at that time due to time zone differences. What do you do?

Situation: I needed a dataset from the US team at 11 am local time, but they were not working due to time zone differences. Task: I had to ensure the data was available to continue my work. Action: I first checked if the data could be pre‑fetched or scheduled for nightly batch export. I set up an automated pipeline that pulls the data from the US environment at 2 am UTC, stores it in a shared data lake, and triggers a notification. I also reached out to the US lead via email and Slack, requesting the data be shared by the end of the day. Meanwhile, I focused on other parts of the project that did not depend on the data, such as writing tests and updating documentation. I used a shared calendar to mark the expected data arrival time and set a reminder for the US team. Result: The data arrived on time, I was able to resume work immediately, and the project stayed on schedule. The proactive automation also reduced future delays.