After upgrading to Starter plan, my Airtable trigger workflows stopped executing automatically when published. They only work on manual execution. Poll time is set to every 1 minute but no executions appear. This started immediately after upgrading.
@Hasan_Diab the plan change knocked your polling trigger out of its registered state even though the workflow still shows active. its a known thing on cloud, the airtable poll stops resuming after a plan upgrade or a platform restart while manual execution still works fine. just deactivate the workflow and activate it again (or open it, make a tiny edit and save), that re-registers the trigger and the 1-min polling picks back up. and dont worry, 1 minute is fine on starter so its not a plan limit, the trigger just needs a kick to re-register.
@Hasan_Diab did u update the webhook to your prod version
When a workflow executes fine in “Test” mode but fails when Published, the issue lies in how the background production listener is registering your trigger node.
To help narrow this down, could you share a bit more context?
What trigger node starts the workflow?
Are production executions set to save? Keep in mind that n8n suppresses successful production logs by default. It might be running without your knowledge. You can change this in the workflow’s specific settings gear icon.
Are you running Self-Hosted or Cloud? If self-hosted, a quick container/server restart often clears out stuck background workers that are caching old draft definitions.
i unpublished it, waited a bit, published it again, still not working. i even tried changing some things, and even tried duplicating it, nothing’s working
if re-registering didnt do it, check whether its actually got anything to fire on. the airtable trigger only executes when it finds a new or changed row since the last poll, it doesnt run every minute by itself, so if nothing has changed in the table since you activated it theres nothing to trigger and youll see zero executions even though its polling fine. add or edit a row in airtable and watch if it fires within a minute, that tells you whether its the trigger thats broken or just no new data to pick up.
it’s a small workflow where i have a airtable trigger that listens every minute to a specific field in a table and sends an email after that. i am running it through n8n cloud
Sounds like a backend provisioning issue. Please reach out to help@n8n.io and raise a support ticket.
Include the following info:
- Workspace ID/Instance URL.
- The specific behavior: “Manual executions work, but all production triggers (including Airtable polling) stopped firing immediately after upgrading to the Starter plan.”
- Confirmation: Mention that you have already tried toggling the workflow off/on and that other scheduled triggers are also not firing.
@Hasan_Diab to be clear, did you actually change that field on a record while it was published? thats the only thing that fires it, the 1-minute is just it polling to check, it doesnt run on its own. if you havent touched the field theres simply nothing to trigger on.
@Hasan_Diab one thing worth double-checking: after deactivating and reactivating, open the Airtable trigger node settings and click “Fetch fields” or just re-save the node settings (even without changing anything) - this forces n8n to re-register the polling scheduler cleanly. Sometimes a plain deactivate/activate cycle doesn’t fully re-initialize the poll if the scheduler state is stale on Cloud.
Also confirm the n8n Cloud execution logs actually show a poll attempt - go to Executions and filter to include “Manual” + “Automatic” to see if any polling runs appear at all. If zero automatic executions show up after 2-3 minutes, the scheduler registration likely didn’t stick and you may need to contact n8n support with the workflow ID since this is a Cloud-side issue.