Background function requests failing with status 503, 504, 408

Only 2 of these requests returned 202 as expected. This background function modifies and delivers PDF files to our users, and it works about 10% of the time. Works great locally.

X-Nf-Request-Id: 01GHDF20Z9624DNV9DDYPXNT8Z
X-Nf-Request-Id: 01GHDF3YZ34QMTV2B7AS10DBVN
X-Nf-Request-Id: 01GHDF7CXZTX65BR57G3CBBJEC
X-Nf-Request-Id: 01GHDFFXMXV33WNT0PVN3BY6S1
X-Nf-Request-Id: 01GHDFFZC61S4JN7APVAX3R3SW
X-Nf-Request-Id: 01GHDG35FWRA1KG376SXZKCHJC
X-Nf-Request-Id: 01GHDGD2K2FX336MAT65C5WKAM
X-Nf-Request-Id: 01GHDGG1T8X51WR0NQXS038JEP
X-Nf-Request-Id: 01GHDGK8KMVJYGDGSNEF8F1W5R
X-Nf-Request-Id: 01GHDGM61E4SESEAMGVEEK683Y

We just launched our new stack last night at midnight so this is quite urgent. Background functions seem to still be in beta, if the feature is not ready for actual use please at least le me know so we can figure out a workaround.

Hi @slegay

Yes, background functions are still in beta so we don’t recommend using them on a production site. Nor would we recommend using any beta feature on a production site.

We can continue to troubleshoot if you’d like, but if a quick resolution is what you need, then I suggest you do look into a workaround at this time.

Do you have a timeframe for a release date? Background and edge functions have been in public beta for 7 months.

We don’t have a time frame at this time.