We have adopted an AL development strategy where we see an AL extension as a module.

This has resulted in great productivity and maintainability in our large development team.

We also support 42 countries with these apps.

But we are now running into limitations of the BC service and related infrastructure. In a support case we got to know that the AVS appsource submision system is no longer capable of handling our submission.

A 30 apps bundle for 42 target countries results in 7500 tasks within AVS .

Idea: Currently we can only supply 1 offerid when submitting apps to appsource , this 1 offerid is connected to 1 list of countries. To decrease our impact on AVS we would like to split up our submission into 4 submissions

a) for the first 10 countries

b) for the next 10 countries

c) next 10

d) next 12

And not trigger a timeout, but the system does not let us do that.

More details below:

Root Cause Analysis

The submission exceeded AVS's 30-minute CreateSubJobs timeout due to combinatorial complexity.

Per official AVS documentation: "AVS creates tasks in proportionality to the amount of apps, resolved releases, and target countries."

Factor

Value

Apps in submission

~30 (Our bundle)

Target countries

42

Resolved releases

6 (27.0 - 27.5)

Estimated tasks

~7,500+