The HubSpot CRM Cards uses a “hubspot.serverless” method exposed for sending proxied serverless requests which sends a native fetch under the hood to iniate and takes conf internally
However, it does not expose said conf by way of user configuration and as such you have no abort controller for maanging in-flight requests that are not yet processed
There are countless cases from this ranging from anything debounced (search, etc) to changing ops and batches for data processing that makes no causing race conditions very messy to manaage
There is a way to get around this ……….. There is an “hsFetch” and of course you can use a native “fetch”, but he entire point of serverless is proxying requests that would other be too sensitive on front end
i.e. – Not exposing your access token and proxying that back from serverless is problematic for security reasons too lengthy to describe.
This is an architectural oversight.
