@Carlos
Absolutely, I'd be glad to assist you with this!
It sounds like you're experiencing an issue with the way Make.com (formerly Integromat) handles new data during the execution of a scenario. Typically, Make.com should trigger your scenario for each new row added to your Google Sheet. If new rows are not being processed when added during an ongoing run, there might be a configuration issue within your scenario settings.
Here are a few steps you can check to ensure your scenario runs correctly:
1. **Triggers**: Make sure your Google Sheets trigger is set up to watch for new rows. You might need to adjust the trigger settings to check for new data more frequently.
2. **Delay Module**: If you have a delay module, ensure that it's configured correctly. The delay might be causing the scenario to miss new rows if they're added before the delay timer resets.
3. **Data Limit**: Check if there's a limit set on the number of rows processed per execution. You might need to increase this limit.
4. **Scenario Execution**: Ensure that your scenario is not set to process data only once. It should be set to run continuously or at specific intervals.
5. **Concurrency & Queuing**: Look into whether Make.com is queuing the scenarios correctly. If multiple instances of the scenario cannot run concurrently, new rows might be missed.
If you've checked all these and the issue persists, it might be a good idea to reach out to Make.com's support for a more detailed investigation into your specific scenario configuration.
Remember, it's important to test your scenario with different conditions after making any changes to ensure it behaves as expected. If you need further assistance with VAPI or have any other questions, feel free to ask!