Asynchronous LLM Calls: Trace Differences in Phoenix Support

Hi Phoenix Support , we're using phoenix for a while now. recently, we built a new app backed by llama-index. Some of the LLM calls there are wrapped by either FunctionCallingProgram or OpenAIPydanticProgram, for working with structured responses. We've noticed that when these programs are called regularly, we can view the named parameters (or inputs) to the program through the traces. However, when we call these program asynchronously, using their acall method, these inputs are not exposed as part of the trace, and the only thing we have there is the formatted template prompt already including the relevant parameters (without being able to see which parameters were sent). Is that a behaviour your familiar with? that asynchronous calls are traced differently from "regular" calls? the implementations of the calls on both cases is identical except for the async llm call.