Summary
The user is developing a workflow using map_task to convert a list of strings into FlyteDirectory objects, which works locally but fails remotely with a URI not being recognized as a directory. This issue does not occur with a single map_task or when using dynamic tasks. The problem is resolved when the innermost task returns a path string instead of a FlyteDirectory. The user notes differences in path patterns between one-level and two-level map_task executions and provides code for the innermost task, indicating the failure with FlyteDirectory and success with a string path. They request to file an issue and seek clarification on the support for mapping over map tasks.