Completely disabling post-processing of deploys

Sure, tis done, will take effect on future deploys.

@fool Please could you disable form processing for 92144c33-d2f2-4e92-8027-1acffcb1400e as well?

Many thanks!

@simonhrogers - done! :slight_smile:

Hi, could you please disable all post processing for 86913a5f-87bf-4e47-bb90-a15c4573331f?

Thank you!

I have disabled form processing there for you, Robby.

Hi Chris,
I also would love it if you could tudn off form processing for our project as well, APP ID 9a96861e-50f2-43eb-82a5-4621ce528390

Thanks very much, and thanks for the info.

Sure thing, tis done.

1 Like

Hi @fool, seems you’re the one to ping on this, would it be possible to disable form post processing for f761f9db-297d-421c-918f-6c6a60e5ad41?

With that and the setting up the our build takes almost 50% longer. For example, the bit that we can control takes 7m 31s and the whole deploy is 14m 33s on 9m 42s build time. Not sure what gets billed the build time of 9m 42s or the deploy time of 14m 33s.

We can certainly work on optimizing this on our end, though for some changes we need to rebuild every page and if we’re getting billed 50% more than what we can control this will add up quite quickly.

We’re on an open source plan, so without further sponsorship it looks like we won’t have enough build minutes for the amount of contributions we’re seeing at the moment.

The time that is billed is shown in the deploy summary on each deploy’s logs page:

Processing time is never counted.

Regardless, I’ve disabled the form processing for your site which was the only piece you couldn’t have controlled already in the UI.

1 Like