i have made 2 scenarios in make.com, in 1 scenario it captures my shopify orders and outbounds a call to the customer. and in the other scenario there is a webhook which captures the endcall reason. the issue is that the webhook is not registering more than 1 orders at once

@LP Gaming It sounds like you're experiencing an issue with concurrent processing of multiple orders through your webhook in Make.com (formerly Integromat). Webhooks by their nature should be able to handle multiple incoming requests, but there might be limitations or configurations within your Make.com scenario that are causing this issue. Here are a few steps you can take to troubleshoot and potentially resolve the problem: 1. **Check Webhook Settings**: Ensure that your webhook in Make.com is configured to handle multiple connections. There might be a setting that limits the number of concurrent connections. 2. **Review Scenario Logic**: Look at the logic following the webhook trigger in your Make.com scenario. If there's a bottleneck or a synchronous operation that requires completion before the next order is processed, this could be causing the issue. 3. **Concurrency and Rate Limiting**: Make.com might have concurrency or rate limiting policies that could affect how many orders your webhook can process at once. Check if there are any such limits and adjust your scenario accordingly. 4. **Error Handling**: Make sure that your scenario has proper error handling to manage multiple requests. If an error occurs with one order, it shouldn't stop the processing of subsequent orders. 5. **Server Performance**: If your webhook endpoint is hosted on a server with limited resources, it might struggle with multiple simultaneous connections. Consider scaling up your server or optimizing its performance. 6. **Contact Support**: If you've gone through these steps and the issue persists, it might be best to contact Make.com support for assistance. They can provide more detailed guidance based on their system's capabilities and limitations. If you need further assistance or have more details to share that could help in troubleshooting, please let me know!

@Vapi it is not working when im using schedule option as start immediately

@LP Gaming If your webhook is not registering more than one order at once when using the "Start immediately" schedule option, it could be due to the way the scenarios are triggered or a limitation in the processing of simultaneous events. Here are some steps you can take to address the issue: 1. **Check Scenario Triggers**: Ensure that both scenarios are correctly set up to trigger as expected. The scenario that captures Shopify orders should trigger a call immediately after an order is placed, and the webhook scenario should be ready to capture the end call reason as soon as the call ends. 2. **Review Webhook Configuration**: Verify that the webhook is correctly configured to accept multiple simultaneous incoming connections. If there's a queuing system or a delay in processing, it might not register all orders at once. 3. **Examine Rate Limits**: Make.com may have rate limits that restrict the number of operations that can be performed in a short time frame. Check if you're hitting any of these limits with your scenarios. 4. **Test with Delays**: As a troubleshooting step, try adding a short delay between order processing to see if that allows the webhook to register each order. This isn't a solution but can help identify if the issue is related to simultaneous processing. 5. **Check for Errors**: Look for any error messages or logs in your Make.com scenarios that could indicate why the webhook isn't registering all orders. Errors can provide clues to what's going wrong. 6. **Contact Make.com Support**: If you're unable to resolve the issue on your own, reaching out to Make.com support may be the best course of action. They can provide insights specific to their platform and help you troubleshoot the issue more effectively. If you've tried these steps and the issue persists, please provide more details or error messages you're encountering, and I'll do my best to assist you further.

@LP Gaming Sorry for the late response. Are you still experiencing this problem? If so, could you share: - The recent call ID - When exactly this happened (the timestamp) - What response you expected to get - What response you actually got instead This would really help me figure out what went wrong!