The 5 day expiration is ridiculous.

When building out a new scenario with a Webhook as the trigger, I invariably only use the trigger a a couple of times at the beginning of my build process, and then I put the incoming data into a JSON module. I then use that as my starting point for testing the scenario as I build it out.

Because the Webhook is technically not set as the trigger for this scenario any more, after five days it expires. Unless I make a point of making it the trigger point again at least every 4 to 5 days. Which is somewhat ridiculous, as I am often working on numerous scenarios over the course of many days or even over weeks.

Today I discovered the webhooks from three scenarios I was working on last week all expired, because five days had passed since those webhooks were set as the current trigger point on the three scenarios. I then had to waste a considerable amount of time setting up three new webhooks.

Make.com needs to rethink this expiration concept. Currently it's a burden for some users to deal with.

One year would be be understandable, but 5 days is way too short!

this just caused me a lot of trouble, I would, sorry NEED to be informed about this! 5 days is also ridiculously short imo

I just had 2 expire with no notification. This is ridiculous that they would expire, but even more ridiculous that you wouldn't automatically send some sort of notification. Instead, theScenario is just broken. The only fix? Set up a new webhook and build the Scenario again. Make should be helping with productivity, not hindering it.

Anna Robinson Brian: Hi Anna & Brian, If you keep your scenario active even if it's not executing the requests this won't expire the gateway URL.

They should never really expire but if you're going to make them do so this is essential.