Data backfill
- Feature of generating retroactive data for nodes
- Why do the retroactive instances of a node that is scheduled by hour or minute not run in parallel after I enable the parallelism feature for the node?
- The retroactive instances of a node are not run after I specify the data timestamp for retroactive data generation. The retroactive instances are in the Pending (Schedule) state and are highlighted in yellow in the DAG. Why does this happen?
- Why do I receive the error message which indicates that the scheduled runtime of a node is not within the specified data timestamp range?
- Why cannot retroactive instances be generated for a node after I enable retroactive data generation for the node?
Resource waiting
Dry-run instances
- What is a dry-run instance?
- Why does a dry-run instance exist?
- Scenario 1: An instance is scheduled to run on a specific day every week or every month
- Scenario 2: An instance is generated in real time but is deprecated
- Scenario 3: The status of an instance is set to successful
- Scenario 4: The property of an instance is dry run
- Scenario 5: An instance is not selected for a temporary workflow
Troubleshoot dry runs for nodes that are scheduled on a daily basis
Nodes that are not run
Node instance status
- What do I do if I cannot find the desired auto triggered node on the Cycle Task page in Operation Center?
- Why cannot I find even one instance of an auto triggered node?
- What do I do if I can find instances of other auto triggered nodes but cannot find even one instance of the desired auto triggered node?
- What do I do if the desired auto triggered node has instances but the instances are not run?
- What are the conditions that must be met to run a node?
Node freezing and unfreezing
Nodes that are successfully run but have no data generated
Nodes that fail to run
- General reference
- I have configured rerun properties for my node, but the node does not rerun after it fails. In addition, the error message
Task Run Timed Out, Killed by System!!!appears. What do I do? - What do I do if the following error is reported for a node when the node is run: OSError:
[Errno 7] Argument list too long?
- I have configured rerun properties for my node, but the node does not rerun after it fails. In addition, the error message
- Errors for MaxCompute nodes
- ODPS-0420095: Access Denied - Authorization Failed [4093], You have NO privilege to do the restricted operation on {acs:odps:*:projects/xxxx}. Access Mode is AllDenied.
- What do I do if the message ODPS-0420061: Invalid parameter in HTTP request - Fetched data is larger than the rendering limitation. Please try to reduce your limit size or column number appears?
- What do I do if the data synchronized by using multiple threads is out of order?
- Errors for AnalyticDB for MySQL nodes
- Errors for database nodes
- Errors for general nodes
- How do I view the logs of a for-each node, do-while node, or PAI node in Operation Center?
- What do I do if the error message
error in your condition run failappears when I run a branch node? - What do I do if the error message
None Ftp connection info!!appears when I run an FTP Check node? - What do I do if the error message
Connect Failedappears when I run an FTP Check node? - What do I do if the error message
The current time has exceeded the end-check time point!appears when I run an FTP Check node? - What do I do if the error message
File not Exists or exceeded the end-check time point!appears when I run an FTP Check node?
- Errors for resource groups