Execution and approval
Review plan inputs and usage, and distinguish agent approval, job submission, and recovery after an uncertain response.
After preparing input, review the execution plan. It fixes the inputs and settings for this run. Creating a plan does not start a job.
Before execution
Open Review in the project's Execution plans list and check the following.
- The tool and reviewed inputs match the intended task.
- Settings, files, chains, and regions are correct.
- Usage count and submission deadline are suitable.
- The current screen allows submission, or explains a restriction.
A price marked Not configured is undecided, not free. Check usage counts and price separately. Without a displayed cost, the amount cannot be confirmed.
Plan IDs and hashes
In agent responses, planId locates the plan and planHash fingerprints the reviewed contents. Together they confirm that the plan submitted is the one reviewed. Preserve the returned values unchanged.
Submission requestKey identifies one submission request and differs from planId and planHash. A lost request key cannot be replaced or inferred using planHash.
- Query the plan and acceptance status.
get_plan({planId: "known-plan-id"})takes only planId, not requestKey or planHash. You can query without the original request key, but the lookup neither returns nor recovers that requestKey. - Check the accepted job. If
submittedJobIdexists, follow its status and detail link. If absent, acceptance is still unconfirmed: submission may still be processing. Absence alone does not prove failure or nonacceptance. - Retry the same request only if you retained it. Use both the original requestKey and identical submission body.
- If the original request is missing, recover records first. Limit work to lookups and finding the original request. Do not immediately submit a new request or plan. Replacing keys or hashes is not recovery.
Submitting the same already accepted plan under another key is rejected with plan_already_submitted. This does not mean every new key for an unsubmitted plan is rejected. Duplicate-plan rejection and recovering the original receipt are different operations. Creating and submitting a new plan can duplicate work for the same inputs.
Changed inputs or settings require a new plan and review; old approval does not cover changes. Even a retained plan can produce different outputs because of model randomness or the execution environment. Matching hashes do not guarantee matching numbers.
Input provenance
Researchers obtain external database materials directly from official sites. Nadoo Bio does not download them on behalf of users from IDs or URLs.
- Upload protein structures as PDB or mmCIF files, then select chains and regions after format inspection.
- Upload FASTA files or enter sequences directly. For molecules, enter your SMILES or select a supported stored file.
- Download permission may differ from permission for commercial computation, external processing, or sharing. Provide data whose terms cover your intended use.
- Keep the source database, identifier, release, download date, and license notice with the original. Passing format inspection does not confirm usage rights.
- Historical input provenance from earlier server lookups remains visible in existing plans. Directly supplied data is not described as verified against the source database. The agent field
get_plan.inputSourcesalso returns only previously recorded sources.
Agent approval and job submission
- Prepare inputs
- Review plan
- Human approval
- Submit job
- Read results
When an agent-created plan needs human approval, Approve agent execution appears. Review and approve it so the agent can proceed with that plan. Approval permits submission; it neither resumes the agent nor schedules a job automatically. The agent must call submit_plan with the approved plan. You do not also need to select Submit job on the web. Current submission conditions are checked again at submission.
Plans prepared directly on the web use a separate path. Review the checks and select Submit job. When Job accepted appears, open View jobs to check progress. Acceptance is not completion of computation.
If approval or submission has expired, follow the screen to review again or prepare a new plan. Changed execution conditions can also prevent submission despite earlier approval.
For Boltz plans made with a Nadoo Bio API key, the user reviews terms and approves the exact plan on the web; the agent then submits with submit_plan. No separate Boltz service key is needed. For multiple sequences, see Preparing Boltz batches.
When a response is lost
Do not immediately create a new plan or request after a missing submission response. If A request needs an acceptance check appears, select Try again. This checks acceptance using the saved request and resends that same request only if it has not been accepted.
Save request is available only while the original request remains on screen and the button is shown. It saves that request to a file; it cannot recover a lost request. The file is neither an execution-completion certificate nor a result file.
If the browser no longer holds the original request, neither downloading nor retrying that request can recover it. Check the screen guidance and job list, then obtain the original request record before submitting anything new. A response that does not match the original request is not automatically replaced with a new request either.
When submission is unavailable
| Situation | Next action |
|---|---|
| Submission deadline expired | Review inputs and prepare a new plan. |
| Execution conditions changed | Review a new plan under current conditions. |
| No access permission | Check the signed-in user and project permissions. |
| Execution environment unsupported | Complete supported input preparation and check current support. |
Input preparation, plan creation, and human approval do not supply a runtime. API-key and web submission support may also differ. See Execution support and next steps for specific response reasons.
Following jobs and results
Check progress and failure reasons in the job list. Agent-provided web links open the relevant page with access checks still applied. When results are available, use Reading results to review metrics, artifacts, and execution evidence together.
Preparing inputs
Choose formats for sequence, structure, and small-molecule files; select chains and regions; and understand what file inspection does and does not check.
Preparing Boltz batches
Prepare multiple plans from single protein sequences in CSV/FASTA, and check inputs, setting combinations, and submission eligibility.