S
MSS
J
d3ec8122f30d4d69a7512199d25ce93b)
JError: Queue send failed: Internal Server Error calling queue.send ? I am retrying a few times backing off on the order of seconds, but the same error is thrown. Should these errors not be considered retryable?
V
VV
SSJS
FF
N
NJ
Promise.allSettled
SserviceOne fails and serviceTwo is on-going, report serviceOne's error to Sentry without waiting serviceTwo to be completedMIt rejects when any of the input's promises rejects, with this first rejection reason.
MS
Sentry.captureException(error); reports error before the request is completed. AFAIK, Sentry reports errors asynchronously, so when you call Sentry.captureException(error); in the finally and let the worker completed, the error might be buffered by Sentry SDK, but not reported yet if I am not missing anything. So you may need to call await Sentry.flush(); after then.
L
J
LLS
OOO
AOOOOJ
.sendError: Queue send failed: ConflictOAM
d3ec8122f30d4d69a7512199d25ce93bError: Queue send failed: Internal Server Errorqueue.sendserviceOneserviceOneserviceTwoserviceTwoSentry.captureException(error);Sentry.captureException(error);await Sentry.flush();Error: Queue send failed: Conflictasync function waitForAll(promises) {
await Promise.allSettled(
promises
.map(p => p.then(
(x) => x,
(e) => {
Sentry.captureException(e);
throw e;
})
)
);
// Not sure it is needed, it might not be needed
await Sentry.flush();
}
async queue(batch, env, ctx) {
try {
// Schedule sending events asynchronously
const eventsPromises = [
serviceOne.sendEvents(batch),
serviceTwo.sendEvents(batch)
];
// Wait event promises without blocking the response
ctx.waitUntil(waitForAll(eventsPromises));
} catch (error) {
// Errors occurred during event sending are already reported to Sentry by "waitAll" above.
// Here we are just reporting other errors if they are.
Sentry.captureException(error);
}
}