Cross-Workflow Trigger and Dependency Analysis Dataset

#Code reasoning #Dependency extraction #Waiting chain analysis #Execution behavior explanation #Distributed job scheduling #Workflow orchestration #Scheduler code review #Dependency chain debugging

4350
0.3GB
JSON
CATL
MOBIUSI INC

Updated:2026-11-04

AI Analysis & Value Prop

This dataset contains source code from distributed task and job scheduling systems that implements dependencies across workflows, including workflow definitions, job scheduling logic, event listeners, external-task waits, and sensor or trigger configurations. It focuses on dependency origins and trigger conditions, enabling analysis of cross-job waiting chains and inference about downstream scheduling, execution, and failure propagation when dependencies are met or released. It is suitable for code-reasoning model training, workflow orchestration analysis, and scheduling-logic explanation.

Dataset Insights

Sample Examples

{}

Technical Specifications

Field	Type	Description
file_name	string	File name
source_code	string	Original source code containing workflow definitions, job scheduling logic, event listeners, external-task waits, and sensor or trigger configurations.
waiting_chains	array	Inferred cross-workflow waiting order and blocking dependencies based on the dependency relationships.
workflow_inventory	array	Workflows, jobs, and their trigger sources identified in the source code.
execution_explanation	string	An integrated code-level explanation of the origins of cross-workflow dependencies, their trigger conditions, waiting chains, and execution behavior after dependency release.
cross_workflow_dependencies	array	Dependencies between workflows or jobs established through events, external task completion signals, sensors, or triggers.
dependency_release_behaviors	array	Inferred scheduling, execution, and failure propagation behavior of downstream workflows and jobs when dependencies are satisfied or released.

Compliance Statement

Authorization Type	Proprietary - Commercial AI Training License (No Redistribution)
Commercial Use	Requires exclusive subscription or authorization contract (monthly or per-invocation charging)
Privacy and Anonymization	No PII, no real company names, simulated scenarios follow industry standards
Compliance System	Compliant with China's Data Security Law / EU GDPR / supports enterprise data access logs

Frequently Asked Questions

What does the dataset contain?: It includes scheduler source code related to cross-workflow dependencies, along with workflow inventories, dependency relationships, waiting chains, post-release execution behaviors, and integrated code-level explanations.

How are cross-workflow dependencies represented?: The data focuses on dependencies established through events, external task completion signals, sensors, or triggers, and analyzes their trigger conditions, blocking order, and downstream scheduling behavior after they are satisfied.

Which model training and application tasks does it support?: It supports code reasoning and code SFT, as well as cross-workflow dependency extraction, waiting chain analysis, scheduling logic explanation, and scheduler code review.

How can I access the data, and what are the licensing terms?: Access methods, available versions, and licensing scope are specified on the product page and in the applicable license agreement. Review the terms before using the data for commercial training, redistribution, or other specific purposes.

Can't find the data you need?

Post a request and let data providers reach out to you.

Get this Dataset

Verified for Enterprise Use

Cite this Work

@dataset{Mobiusi2026,
  title={Cross-Workflow Trigger and Dependency Analysis Dataset},
  author={MOBIUSI INC},
  year={2026},
  url={https://www.mobiusi.com/datasets/70d31d006c4d733b7f858f2c9fd3a2c9},
  urldate={2026-10-27},
  keywords={cross-workflow dependency dataset,workflow scheduling source code,cross-job waiting chains,scheduling dependency analysis,event-triggered workflows,external task dependencies,code reasoning training data,workflow execution behavior},
  version={1.0}
}

Using this in research? Please cite us.

placeholder

Scene

Domain

Modality

Task