Extension signing validation timeout

Hi AMO Team,

We are using web-ext@10.0.0 to sign our Firefox extension as part of our automated CI/CD build pipeline.

Recently, we have been encountering intermittent timeout failures during the waiting for validation.. phase. To mitigate this, we increased our --timeout flag value to 900000 ms ( 15 minutes). However we are still seeing intermittent build drops even though our packaged extension is quite light-weight around 140 KB in size.

Could you please provide guidance on the following:
Ideal --timeout value: What is the recommended maximum threshold we should set ?

Explicit --approval-timeout: Do we need to explicitly declare the --approval-timeout argument alongside --timeout. If yes, what would be ideal value for this ?

Any insights or recommended platform best practices for automated signing pipeline would be greatly appreciated.

Our build VM is Ubuntu and we are running the build jobs inside a docker container.

Thanks

Unfortunately, I think the --timeout flag was added many years ago when submission times were more stable. There’s currently no guarantee that submissions will be signed within a given time period.

I think your best bet might be to set up a separate cron job to poll for the version detail endpoint for status updates. See the Authentication (External) page for information about how to authenticate against this API.