If actions that rely on third-party services are not executing, a common cause is that your Glide Team has run out of Updates.
When a Team runs out of Updates, Glide temporarily stops executing Update-based actions. This can prevent third-party actions from running, even though they appear correctly configured.
Examples of affected actions include:
Call API
Trigger Webhook
Actions that use third-party integrations such as DocsAutomator, PDFMonkey, or similar services
This condition is not limited to third-party actions and may also affect Glide AI, workflows, and data syncing.
To understand why this happens, what else is affected, and how to restore functionality, see:
Once Update availability is restored, third-party actions should begin executing normally.