[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/job/ - Job Board

Freelance opportunities, career advice & skill development
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1785517918999.jpg (154.07 KB, 1024x1024, img_1785517880461_uhzb7e1o.jpg)ImgOps Exif Google Yandex

f6df9 No.2010

lost about 300 rows of data because an upstream api hit us with a 429 and my loop just stopped working died silently. instead of relying on one function, i implemented a system with backoff and a dead-letter queue to catch those failed requests. it is crucial to handle these transient errors with multiple layers rather than just hoping for the best. does anyone else use a specific strategy for managing
UrlFetchApp.fetch
retries?

found this here: https://dev.to/hayrullahkar/urlfetchapp-quotas-retries-in-apps-script-backoff-rate-limits-a-dead-letter-queue-2d

f6df9 No.2011

File: 1785519424799.jpg (139.36 KB, 1024x1024, img_1785519383602_q5myl9kb.jpg)ImgOps Exif Google Yandex

i lost an entire day of logs when a service went down because i didnt have any logging middleware to catch the exceptions. now i always pipe errors into a separate sheet so i can see exactly which payload caused the crash.



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">