You set up a Notion database automation to trigger when a Status property changes, but the automation simply does not run. The root cause is usually a mismatch between the automation trigger configuration and the actual way you are changing the status value. This article explains the specific trigger conditions that must be met and provides a step-by-step fix to get your automation working again.
Key Takeaways: Fix a Notion Database Automation That Ignores Status Changes
- Automation trigger > When a property is edited > Status: The automation only fires when the Status property value is changed from one option to another.
- Manual edit vs. formula/bulk edit: Automations do not trigger when a Status value is changed by a formula, a rollup, or a multi-select bulk edit.
- Database view filter interaction: A filtered view can hide the automation execution; always test with a full table view.
Why a Notion Automation Does Not Trigger on Status Change
Notion automations rely on explicit property edits. When you configure an automation with the trigger “When a property is edited” and select the Status property, the automation waits for a direct user action that changes the Status value. The automation does not fire if the Status changes due to a formula, a rollup from another database, a template button, or a bulk edit that updates multiple database rows at once. Additionally, if the automation is set to run only when a specific Status value is selected, the new value must match that condition exactly, including letter case and spacing.
Another common cause is the automation scope. Automations run only for the database they are created in. If you are editing a linked database view or a database that is part of a template, the automation may not see the change. The automation also requires that the user editing the Status has at least Can Edit access to the database. A user with Can View access cannot trigger automations.
Trigger Condition Specifics
When you set up an automation trigger, you choose one of three conditions:
- Status is edited to any value – fires when the Status changes from any option to any other option.
- Status is edited to [specific option] – fires only when the Status changes to the named option.
- Status is edited from [specific option] – fires only when the Status changes away from the named option.
If you select the second or third condition, the automation will not fire if the new value does not match the specified option. For example, if you set “Status is edited to Done” but you change the Status to Complete, the automation will not run.
Steps to Diagnose and Fix a Notion Automation That Does Not Run on Status Change
- Open the automation configuration
Go to the database where the automation is set up. Click the three-dot menu in the top-right corner of the database view, then select Database automations. Find the automation that is not running and click its name to open the editor. - Verify the trigger property and condition
In the trigger section, confirm that When a property is edited is selected and that Status is the chosen property. Check the condition dropdown. If you selected a specific Status value, make sure that value exactly matches the Status option in your database, including capitalization and spaces. For example, “To Do” is different from “To-do”. - Test with a manual edit in a full table view
Switch your database view to a full table view with no filters. Manually click the Status property of a row and select a different value. Wait 30 seconds. If the automation does not run, the trigger condition is likely incorrect. If it does run, the problem is with your filtered view or the method you used to change the Status. - Check if the Status change comes from a formula or rollup
If the Status property is populated by a formula or a rollup from another database, the automation will not fire. Automations only respond to direct manual edits. To fix this, remove the formula or rollup from the Status property and require manual entry. Alternatively, use a separate formula property for the calculation and keep Status as a manually editable field. - Review automation action and permissions
Click the action section of the automation. Ensure the action (for example, Send notification or Create a page) is configured correctly. Then verify that the user who is editing the Status has Can Edit access to the database. Go to Settings & Members > Members and check the user’s role. Only members with Edit permission can trigger automations. - Recreate the automation if it still does not work
Delete the non-working automation by clicking the three-dot menu next to its name and selecting Delete. Create a new automation from scratch. Sometimes automations become corrupted due to database structure changes. A fresh setup often resolves the issue.
If Notion Still Has Issues After the Main Fix
Automation runs but no visible result
The automation may be executing but the action is not producing a visible outcome. For example, if the action is “Send notification to a person,” the recipient may have notifications muted or the notification may go to the Notion inbox. Check the Notion inbox for the database. Also, if the action is “Create a page in a database,” verify that the target database exists and that the user has Can Edit access to it.
Automation runs multiple times for one edit
This usually happens when there are multiple automations configured with the same trigger. Review all automations in the database. Delete or disable duplicate automations. Also, if you have a template button that also changes the Status, the automation may fire once for the manual edit and again for the button action. Use only one method to change the Status.
Automation does not fire when Status is changed from a linked database
Linked database views show data from another database. Automations are tied to the source database, not the linked view. To trigger an automation on a Status change, you must edit the Status directly in the source database. If you must trigger from a linked view, create the automation in the source database instead.
Notion Automation Trigger Types Compared
| Item | When a property is edited | When a page is added |
|---|---|---|
| Trigger condition | User manually changes a specific property value | A new page is created in the database |
| Works with Status change | Yes, only for direct manual edits | No, this trigger does not respond to property changes |
| Works with formula/rollup | No | N/A |
| Works with bulk edit | No | No |
| Works with template button | No | Yes, if the button creates a new page |
If you need an automation to run when a Status changes due to a formula or a bulk edit, no direct fix exists. You must redesign your workflow so that the Status is always changed manually. Consider using a button that changes the Status and then triggers a separate automation via the “When a page is added” trigger if applicable.
Now you can identify why your Notion database automation does not run on a Status change and apply the correct fix. Test the automation by manually editing a single row in a full table view. For advanced workflows, avoid using formulas or rollups on the Status property that you intend to use as an automation trigger. Instead, keep a separate formula field for calculations and leave the Status field for manual input only.