โ08-26-2025 08:30 AM - edited โ08-27-2025 09:02 AM
[UPDATE 27-Aug-2025] Workato's support team is already looking at this situation. [/UPDATE]
Hello everyone,
After several attempts I'm not able to understand what's going on, hence my question here.
I've built a connector to access Workato Developer API and it has a trigger named "Deployment complete", which uses the list deployments endpoint (GET /api/deployments) to pool for new deployments. According to documentation (FAQ 5), this endpoint only works from DEV and I've created an API client with all permissions to DEV environment.
I've created a recipe and started it in DEV environment. It works pretty well, triggering correctly when there's a new deployment (it polls every 15min).
The problem appeared when I created a second recipe, with the same trigger, same connection config...and it never triggers.
Does anyone have idea why? Can it be some Workato limitation?
I appreciate your time and effort to help me sort this out.
Thanks!
Solved! Go to Solution.
yesterday - last edited yesterday
Hello everyone!
There was indeed something on Workato's side and the issue is now fixed.
Thanks everyone who tried to provide solutions, which unfortunately were not the answer.
Cheers.
โ08-27-2025 10:55 AM
Hmm, yes that makes sense. It does look like it might be a limitation of the Developer API. Please let me know if you happen to find a workaround or solution.
โ08-27-2025 09:02 AM
Workato's support team is already looking at this situation and there's a support ticket raised by them.
โ08-29-2025 08:25 AM
Hi @saraiva ,
In workato API endpoint can be liked to only recipe only . If we want to attach another recipe it won't be possible in workato . Again we need to create new API endpoint and link to recipe .Few days back, I have also faced same issue and later known on limitation
Thankyou
4 weeks ago
I want to inform that Workato Support team is still working actively on this situation.
yesterday - last edited yesterday
Hello everyone!
There was indeed something on Workato's side and the issue is now fixed.
Thanks everyone who tried to provide solutions, which unfortunately were not the answer.
Cheers.