What the data for this category looks like
The data for securities financing daily reports comes from public margin trading disclosure documents from the Shanghai and Shenzhen Stock Exchanges and the National Equities Exchange and Quotations, as well as end-of-day settlement data from securities registration and settlement institutions. Updates are released 1 to 2 hours after market close on trading days, with no updates on non-trading days. Each daily report is sorted by market category, and includes fields: security code, security abbreviation, financing purchase amount, financing repayment amount, financing balance, securities lending sold volume, securities lending remaining volume, securities lending balance. All units are uniformly Renminbi Yuan. Stocks listed on the Beijing Stock Exchange will additionally mark the trading unit as shares.
What constraints do these characteristics impose on workflow orchestration?
The requirement for scheduled updates on trading days means workflows must only trigger on trading days, to avoid empty data tasks running on non-trading days. The structure with multiple fields and clear units means parsing nodes in the workflow must strictly match field names and unit rules, to prevent numerical statistic errors. The large number of margin trading targets across the entire market means workflow configurations must include batch fetching and processing logic, to avoid single request timeouts. Public disclosure documents may have minor format adjustments, so configuration space for fault-tolerant parsing must be reserved.
How to configure settings
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
workflow_trigger_cron | 0 0 18 * * 1-5 | Matches execution at 18:00 on trading days, when financing daily reports have completed updates and been released |
batch_fetch_count | 50 items per request | The large number of margin trading targets across the entire market means fetching too many items in a single request will trigger interface timeout restrictions |
strict_parse_mode | Enabled | Financing daily reports have many fields and fixed units; strict parsing avoids field matching and numerical statistic errors |
node_timeout_seconds | 600 seconds | Fetching and processing full market data in batches requires a longer execution cycle |
visibility_control | Custom visibility range | Some outputs need to hide original disclosure sources and only retain processed financing analysis results |
llm_tool_call_enabled | Enabled | Public data interfaces are required to pull original financing daily report content; tool calls enable automated pulling |
The parameter values provided on this page are common starting points for configuration. Actual values are affected by material format, data volume and business rules. Specific issues require case-by-case analysis. It is recommended to test on your own samples before finalizing settings.
Three common configuration errors
- Symptom: Workflow returns empty fields or incorrect numerical units. Cause:
strict_parse_modeis not enabled, leading to confusion between field matching rules for financing purchase amount and financing balance during parsing. - Symptom: No node content appears in the interface after importing a workflow template. Cause: Node configuration parameters were not fully saved when exporting the template, or associated data source configuration was not checked during import.
- Symptom: Unexpected results are returned when using
deepseek-r1as the tool calling model. Cause:batch_fetch_countis not configured to adapt to full market securities data volume, leading to incomplete parsed data received by the model.
How to confirm correct configuration
- Trigger the workflow manually once, and verify if node logs include expected fields such as security code and financing balance to confirm parsing rules match the data structure.
- Review trigger configurations to confirm that trigger times match the financing daily report update schedule, avoiding execution on non-trading days.
- Check visibility settings to confirm that original disclosure content that needs to be hidden has been properly filtered, and output content meets usage requirements.
- Test the tool calling node to confirm that financing daily report data can be pulled normally, with no timeout or interface error reports.
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-14.