Data for this category
The data for oil and gas exploration and development declaration materials and file review primarily comes from on-site collected well logging data, drilling reports, reserve assessment documents, approval files, and similar materials. Data update frequency adjusts based on project progress phases. It is updated in batches according to approval nodes during a single declaration cycle. The document structure includes fixed fields such as file number, exploration block number, well ID, declaration date, and approval node records. Attachments are mostly well logging images, core scans, and technical report PDFs. Fields include professional attributes such as latitude and longitude (degrees minutes seconds format), reserve volume (tons/cubic meters), file size, and upload time.
Constraints imposed on workflow orchestration
A large number of professional images and large-volume technical documents are included in attachments. The workflow must support triggering specific processing nodes based on attachment types to avoid unnecessary resource consumption. Format requirements for professional fields require embedding validation rules in the workflow. This ensures entered data complies with oil and gas industry standards. Version association requirements for declaration files require the workflow to bind the corresponding file ID. This prevents data confusion. The requirement for professional term matching in the global knowledge base requires passing the knowledge base ID via configuration items. This ensures the call uses an oil and gas exploration-specific knowledge base. In addition, a single declaration has many process nodes. The workflow must set a reasonable timeout period to adapt to complex review processes.
Configuration settings
Reference only; verify against the target FastGPT release and deployment documentation.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
| Maximum file size for file upload nodes | 1000 MB | Matches the conventional upper limit for single attachments in oil and gas exploration declarations |
| Image transcoding trigger rule | Execute only when attachment suffixes are .jpg/.png/.tif | Adapts to image attachment types such as well logging images and core scans |
variables configuration | Pass global knowledge base ID and exploration well ID fields | Meets knowledge base association and professional field validation requirements |
nodeId configuration | Bind approval node update node ID | Ensures the workflow proceeds in accordance with the approval process sequence |
| Workflow timeout period | 600–1200 seconds | Adapts to complex processing durations for multi-node reviews |
| Field validation rules | Validate latitude and longitude, reserve units according to oil and gas industry standards | Ensures entered data complies with professional specifications |
Three common configuration errors
- The workflow prompts "Knowledge base not found" during execution. The symptom is that the knowledge base call node returns a 404 status code or empty results. The cause is failure to pass the knowledge base ID to the workflow via
variables, or failure to correctly bind the global variable to the oil and gas exploration-specific knowledge base. - The image to base64 node fails to execute. The symptom is that the node status shows an error, and the attachment content is empty. The cause is failure to configure the trigger rule for only image types. Non-image files are forced to undergo transcoding, leading to format errors.
- API calls to the workflow return parameter errors. The symptom is the interface returns "missing required field". The cause is failure to pass the declaration file ID as a
variablesparameter to the workflow node as required.
How to verify correct configuration
- Upload a standard oil and gas exploration image attachment to trigger the workflow. Check the node logs to confirm base64 encoding was generated successfully.
- Call the workflow API with preset knowledge base ID and file ID parameters. Check that the interface returns a workflow instance status of running.
- Enter the workflow configuration page. Confirm that the binding configurations for
variablesandnodeIdmatch the preset parameters. - Upload a non-image attachment. Confirm that the workflow does not trigger the image transcoding node to avoid unnecessary execution.
The values provided are common starting points and should be measured against the reader's own samples.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-09-28.