Great to hear! Enjoy your experience!

I suspect the issue stems from receiving a high volume of events via MQTT, and callin.io initiating a new workflow execution for each one. To addres...

Uh no, apologies. We don't actually anticipate that occurring for at least another 1-2 months.

Ah yes, that makes sense. Modifying that would unfortunately be a breaking change. For the time being, could you please rename "id" to "Id" or "ID"? ...

Just fixed the issue. It will be included in the upcoming release. I'll post an update here once it's available.

Thank you very much. The video was quite helpful. I was able to replicate the issue now. It certainly appears to be a bug. We will investigate and aim...

Ah yes, additional options are now also available. Previously, only 360p was listed among the options. It's possible they become available over time. ...

Apologies, but the current quality is extremely poor (360p), making it impossible for me to discern anything. Could you please provide the rewritten...

Correct, it should typically initiate one workflow execution for each message. This also appears to be what's happening in the video. You sent 3 messa...

Apologies, I don't quite grasp your meaning. I'm uncertain at the moment if it's feasible for multiple messages to arrive concurrently. If this is t...

That's peculiar. I actually tested the RabbitMQ node earlier today, and when I sent three distinct messages, I received three distinct messages as wel...

Released with callin.io@0.111.0

Released with callin.io@0.106.0

Welcome to the community! Unfortunately, that's not currently possible as it hasn't been a requirement for any services integrated with callin.io to...

Yes, your setup is not complete. You can find instructions for a production setup here: Docs Server Setup | callin.io Docs callin.io is an ext...