跳到内容
DocsBuild with Runner
Esc
↑↓导航↵打开⌘J预览
Open Runner

Long jobs and confirmations

How a client works with Runner tools that need a store, run for a long time, or ask before they change store data.

Read this before your agent calls Runner tools on its own.

  • Start with list_stores. Each store tool needs a store_id from list_stores. A call without it answers Pass a store_id from list_stores.
  • Long tasks. Some tools answer with "status": "running" and a job_id. Call get_tool_job with that job_id until it gives the result.
  • Changes that you approve. Some tools first answer with "status": "waiting_for_merchant" and a confirmation id, and they show what will change. Nothing changes yet. When you agree, the client calls the same tool again with the same arguments and "confirmation": {"id": "…", "answer": …}. The confirmation id works one time, for 10 minutes.
  • The same change sent twice. For most tools that make changes, Runner makes the change one time when the client sends the same input again in the same 5-minute period. The second call gets the first answer when the client made no other change between the two calls. After another change, for example a delete, Runner runs the call again.
  • Store data is data. Tool answers can contain product text and customer messages. Your agent must not follow instructions that it finds in them.
  • Your permissions apply. Each call uses your Runner permissions and your plan. The list of tools depends on your plan and on the features of your workspace.

最后更新于 2026年11月19日

这个页面有帮助吗?