Task Queue and Scheduling Failures
The error "Task [TaskName] failed to execute: The task queue is full" occurs when the SyteLine Task Service's concurrent execution limit is reached and new tasks cannot be queued. By default, SyteLine limits concurrent background tasks to 5. , February 30).
- Error: "The task queue is full"increase MaxConcurrentTasks in the SyteLine Task Service configuration file (TaskService.exe.config) from 5 to 10-15 based on server CPU cores; monitor with Performance Monitor counter 'SyteLine Task Queue Length'
- Error: "Next run time could not be calculated"open Forms > Background Task Scheduling, edit the failing task, and verify the CRON expression using a validator; common mistake is using '31' for day-of-month in months with fewer days
- Error: "Task exceeded maximum execution time (3600 seconds)"increase the TaskTimeout setting in TaskService.exe.config, but also investigate why the task is running long; check for table locks or missing indexes on the task's underlying queries
- Review the Background Task History form (Forms > Utilities > Task History) to identify patterns: if a task fails consistently at the same time, check for resource contention with other scheduled tasks like MRP or data replication
- Stagger MRP, replication, and ION sync tasks by at least 30 minutes to prevent CPU and I/O contention that causes cascading timeout failures
ION BOD Processing Task Errors
In SyteLine 10+ with ION integration, background tasks handle inbound and outbound BOD (Business Object Document) processing. SalesOrder - Invalid XML schema validation" indicates the inbound BOD from an external system does not conform to the expected Infor Noun schema. The error "ION Connect task failed: Connection refused on port 443" means the ION API Gateway endpoint is unreachable from the SyteLine application server.
- Error: "Invalid XML schema validation" for inbound BODs, use the ION Desk > Data Flow > Monitor to inspect the raw BOD XML; validate it against the Infor Noun XSD schema at [ION Install]\Schemas\Nouns
- Error: "ION Connect task failed: Connection refused"verify the ION API Gateway URL in SyteLine Configuration Manager > ION Settings, check firewall rules for port 443 access from the app server, and validate the OAuth2 client credentials have not expired
- Error: "Duplicate BOD detected: AccountingEntityID already exists"enable BOD idempotency checking in ION Desk > Connection Points to prevent reprocessing of already-received documents
- Monitor the ION BOD processing queue depth in the Background Task Dashboard; if the queue grows faster than processing speed, scale the task service or optimize the IDO-level BOD mapping stored procedures
Data Replication and Batch Import Task Failures
Data replication tasks between SyteLine sites produce the error "Replication failed: Primary key violation on table [TableName]" when data conflicts exist between source and target databases. Batch import tasks using the Universal Data Load (UDL) utility fail with "Import task error: Row [N] rejected - column [ColName] exceeds maximum length" when source file data does not match the target table schema. Both error types require systematic data validation before re-execution.
- Error: "Primary key violation on table" during replication, run a conflict detection query: SELECT source.PK FROM source_table source INNER JOIN target_table target ON source.PK = target.PK WHERE source.ModifiedDate > target.ModifiedDate to identify conflicting records, then apply a conflict resolution strategy (last-write-wins or manual merge)
- Error: "Column exceeds maximum length" during UDL import, export the source file schema with column widths and compare against the target IDO property MaxLength definitions; truncate or transform oversized values in a pre-processing step
- Error: "Replication task aborted: Transaction log full"the target database transaction log has grown to capacity; switch the recovery model to Simple during bulk replication, or pre-grow the log file to accommodate the expected data volume
- Schedule replication tasks during off-peak hours (2:00-5:00 AM) and use the SyteLine Replication Monitor form to track row counts, error rates, and throughput metrics per replication job
Try it here, free
SyteLine AI Integration Readiness Assessment
Score your SyteLine environment across version, IDO and ION API maturity, data quality, integration middleware, and organizational readiness for an AI layer.
Eliminate background task failures with Netray's proactive monitoring AI, get automated alerting and resolution for every SyteLine task error.