Pauline P. Narvas Hey, @lennsend170683-4600! Welcome 👋 Quick debugging steps: Open browser DevTools Console and check for errors when switching tabs Look for event listeners on window.blur, document.visibilitychange, or similar Try disabling browser extensions that might interfere Check if the issue happens in all browsers or just one For a proper fix, you’ll likely need to update how your CRM handles state persistence. Let us know!
Lennsend170683 4600 Hi Pauline, I honestly have no idea what Im looking at sorry. Is this any help? Regards Lenn
Lennsend170683 4600 @pawlean not sure if that was any help at all?
Pauline P. Narvas Where is it in the docs? Can you share a link?
Ward Van Laer “In push mode, you can set a maximum concurrency per consumer group. This limits how many messages can be in-flight simultaneously for that group. If the limit is reached, Vercel holds back delivery until an in-flight message is acknowledged or its lease expires.“ vercel.com/docs/queues/concepts
Vicent Galiana We are encountering this limitation in a production-like workload using @vercel/queue 0.5.0 and a JavaScript queue/v2beta push consumer. One publish operation created 110 messages. Vercel started all 110 first-delivery callback invocations within 18.354 seconds. The consumer calls a rate-limited downstream GraphQL service, and 49 deliveries failed with HTTP 429 and required retries. We need to configure the push consumer group with a maximum concurrency of 1. The documentation states: “In push mode, you can set a maximum concurrency per consumer group.” However, we cannot find a supported conf
Carter Turnbull 2nd this. It would be a great feature that would drastically improve the loop between non technical team members and UX/UI polishes.
Baptiste 3322 Please 🙏 would be awseome
Akshay Dodeja Give how Vercel Toolbar was created pre AI -- this feature is basically useless without Agents being able to access the data. Does anyone at Vercel engineering use vercel toolbar comments?