Production plan batch scheduling API calls timing out, causing manufacturing delays

ERP Infor CloudSuite
, , , , , , , ,
1

Our production scheduling automation is failing due to consistent API timeouts. When we submit batch scheduling requests via the REST API, the calls take over 30 seconds and eventually timeout. This happens consistently across all batch sizes.

Backend logs show slow database queries during the scheduling process. The production plan involves 200+ work orders with complex routing requirements. This is causing significant manufacturing delays as we can’t generate daily schedules automatically. The UI scheduling tool works but takes 2-3 minutes to complete the same operation. Anyone dealt with similar performance issues in ICS 2022 production planning APIs?

2

The slow queries are likely due to complex routing calculations. Enable query profiling in CloudSuite admin to see which specific queries are slow. In our implementation, we found that material availability checks were causing most of the delay. Consider pre-validating material availability before calling the scheduling API.

3

Your timeout issues with batch scheduling API calls taking over 30 seconds, combined with slow backend queries, require a multi-faceted optimization approach. Here’s how to address all three focus areas:

1. Handling Batch Jobs Taking >30 Seconds:

Switch to asynchronous processing mode. The synchronous API isn’t designed for 200+ work orders:


POST /api/v2/production/schedule?async=true
GET /api/v2/jobs/{jobId}/status

This returns a job ID immediately, then you poll for completion. Set polling interval to 5-10 seconds.

2. Resolving Consistent API Timeouts:

Implement batch chunking strategy:

  • Split 200 work orders into batches of 30-40 each
  • Process batches sequentially or with controlled parallelism (max 3 concurrent)
  • This reduces memory footprint and query complexity per call
  • Total processing time may be similar but eliminates timeouts

3. Addressing Slow Backend Queries:

The logs showing slow queries indicate database optimization needs:

Immediate fixes:

  • Run database statistics update: CloudSuite Admin > System Maintenance > Update Statistics
  • Check for missing indexes on production_orders, work_order_routing, and material_requirements tables
  • Review execution plans for queries taking >5 seconds

Configuration optimizations:

  • Reduce scheduling horizon: Instead of calculating full routing for all orders, limit lookahead to 2-4 weeks
  • Disable unnecessary validation checks: Set production.scheduling.validateInventoryOnSubmit=false if you pre-validate
  • Enable result caching: `production.scheduling.cacheRoutingData=true API call optimization:
  • Include only required fields in response using field selectors: `?fields=orderId,scheduledDate,status
  • Pre-filter work orders by status before API call to exclude completed/cancelled orders
  • Use incremental scheduling: Only reschedule orders that changed since last run

Monitoring and troubleshooting: Enable detailed API logging to identify bottlenecks:

  • Set log level to DEBUG for production.scheduling package
  • Monitor query execution times in database logs
  • Track API response times in CloudSuite Integration Monitor

The combination of async processing, batch chunking, and database optimization should reduce your processing time from 30+ seconds to under 15 seconds per batch, eliminating timeouts while maintaining automation reliability.

4

For batch operations taking over 30 seconds that timeout consistently, you need to switch to asynchronous processing. The production planning API supports async mode where you submit the request and poll for results. This prevents timeouts and handles long-running calculations better. Use the async=true parameter and check status via the job monitoring endpoint.