Hello Bubble Community,
I hope this message finds you well. I’m currently experiencing an issue with a Bubble.io workflow that I’m hoping someone might be able to assist me with.
I have a workflow set up to trigger a Zapier zap (Zap ID = “create ACP”), which is designed to generate a Google Document for a specific ISO 27001 policy. While I have two other similar zaps working fine, I’m running into trouble with a third one.
Here’s the situation: I duplicated a working zap (acceptable use policy), and then modified the new zap to handle a different policy. The trigger in Bubble.io was changed to “create acp” and is associated with my Access Control Policy data type. However, during testing, the zap seems to be pulling data from the original record (Acceptable Use Policy) instead of the new one (Access Control Policy).
Here are the troubleshooting steps I’ve taken:
- Double-checked the Bubble.io trigger (“create acp”), and confirmed it’s working correctly and associated with the correct data type.
- Refreshed the trigger data in Zapier.
- Set up the Bubble.io trigger again in Zapier.
Despite these steps, the issue persists (update : I managed to setup 5 zaps correctly, but the issue goes on for 4 other ones, and I litteraly follow the exact same procedure to deploy this workflow). I’m at a loss as to what might be causing this, so any advice or suggestions from the community would be greatly appreciated.
I suspect that the error comes from bubble side, despite triggers setup correctly.
Looking forward to hearing from you.