Non-blocking agent functions with Temporal?

[darugar]

Is there an example of a function (as in a function available to an agent) that does not block temporal workflows?

I have a function that runs a commandline utility (whois) to check if a domain is registered. I'm making it available to the agent workflow via functions. This causes the workflow to run into the following issue: [TMPRL1101] Potential deadlock detected: workflow didn't yield within 2 second(s).

How do I create a a non-blocking / deadlock causing version of this function?

For now I've converted it to an MCP server, but it seems painful to make every utility MCP.

def is_domain_registered(domain: str) -> bool:
...
        result = subprocess.run(
            ["whois", domain],
            capture_output=True,
            text=True,
            timeout=10
        )
...
        return is_registered

...

    @app.workflow_run
    async def run(
...
        my_agent = Agent(
            name=data.slug,
            instruction=data.instruction,
            server_names=data.server_names,
            functions=[is_domain_registered,]
        )

[saqadri]

@darugar thanks for reporting!

What you are describing should be possible, though I need to double check if the functions will do the right thing within the agent.
One thing you should consider is marking is_domain_registered with @app.workflow_task. Functions marked with that will get executed as activities.

To be super sure, you could create a helper function

def is_domain_registered_impl(domain: str) -> bool:
...
        result = subprocess.run(
            ["whois", domain],
            capture_output=True,
            text=True,
            timeout=10
        )
...
        return is_registered

def is_domain_registered(domain: str, context: Context) -> bool:
    executor = context.executor
    result = await executor.execute_activity(is_domain_registered, domain)
    return result

This will guarantee that we run the function as an activity.

BTW, we have a few new syntactic sugar approaches that may make it a lot easier to define workflows. Check out the @app.tool and @app.async_tool decorators in this example:

https://github.com/lastmile-ai/mcp-agent/blob/main/examples/mcp_agent_server/temporal/main.py#L96-100

This automatically sets up the function to be run as a temporal workflow. You can again use the executor.execute_activity function to run sub-functions as activities, or decorate using @app.workflow_task. Just FYI if that makes your code simpler.

Please let me know if the above helps, and if not happy to pair with you and investigate more carefully.