OptionalcauseReadonlycodeOptionalstackReadonlyVendorThe vendor's own explanation, surfaced to the operator verbatim.
StaticstackThe Error.stackTraceLimit property specifies the number of stack frames
collected by a stack trace (whether generated by new Error().stack or
Error.captureStackTrace(obj)).
The default value is 10 but may be set to any valid JavaScript number. Changes
will affect any stack trace captured after the value has been changed.
If set to a non-number value, or set to a negative number, stack traces will not capture any frames.
StaticcaptureCreates a .stack property on targetObject, which when accessed returns
a string representing the location in the code at which
Error.captureStackTrace() was called.
const myObject = {};
Error.captureStackTrace(myObject);
myObject.stack; // Similar to `new Error().stack`
The first line of the trace will be prefixed with
${myObject.name}: ${myObject.message}.
The optional constructorOpt argument accepts a function. If given, all frames
above constructorOpt, including constructorOpt, will be omitted from the
generated stack trace.
The constructorOpt argument is useful for hiding implementation
details of error generation from the user. For instance:
function a() {
b();
}
function b() {
c();
}
function c() {
// Create an error without stack trace to avoid calculating the stack trace twice.
const { stackTraceLimit } = Error;
Error.stackTraceLimit = 0;
const error = new Error();
Error.stackTraceLimit = stackTraceLimit;
// Capture the stack trace above function b
Error.captureStackTrace(error, b); // Neither function c, nor b is included in the stack trace
throw error;
}
a();
OptionalconstructorOpt: FunctionStaticprepare
Thrown by a connector when the vendor says THIS account cannot serve an object it nonetheless lists in its catalog (e.g. a record type the account has not enabled). Distinct from a fetch failure: retrying cannot help WITHIN a run, so the map ends cleanly instead of climbing a retry ladder — one warning, watermark untouched.
It is deliberately not remembered ACROSS runs. The next run simply asks again, which is what makes an account change self-healing with no marker, no recheck clock and no override to get right.
Connectors are NOT required to import this class — the engine also recognises any error carrying
code === 'OBJECT_UNAVAILABLE', so a connector can classify one without a peer version bump.