Push Notifications deployment fails before Cloud Build with HTTP 409

[zeimpekakhmaria-maker]

Can we access your project?

• I give permission for members of the FlutterFlow team to access and test my project for the sole purpose of investigating this issue.

Current Behavior

Push Notifications deployment fails every time in App Settings > Push Notifications.

FlutterFlow displays:

“Deployment Failed
Unknown error. Please contact support@flutterflow.io.”

The deployment request to tm-prod.dreamflow.cloud/.../run returns HTTP 409.

No new execution is created in Google Cloud Build History after clicking Deploy, indicating that the deployment fails before reaching Firebase Cloud Build.

The following have already been verified:

• Firebase Blaze plan is active.
• Google Cloud Billing is active and paid.
• firebase@flutterflow.io has Editor, Cloud Functions Admin, and Service Account User roles.
• Default Compute and App Engine service accounts have Editor.
• Firestore Rules are deployed.
• Firestore Indexes are deployed.
• Cloud Functions Region is explicitly set to us-central1.
• The deployment was also tested in Incognito mode.

The issue still occurs.

Expected Behavior

Clicking Deploy in App Settings > Push Notifications should deploy the required Firebase Cloud Functions successfully and change the Deployment Status to Deployed.

The deployment should reach Google Cloud Build and complete without returning HTTP 409 or “Deployment Failed – Unknown error”.

Steps to Reproduce

1. Open the FlutterFlow project “deliverysystem”, connected to Firebase project delivery-app1-b4b7c.
2. Go to App Settings > Firebase and verify that Cloud Functions Region is set to us-central1.
3. Go to App Settings > Push Notifications.
4. Enable Push Notifications.
5. Click Deploy once.
6. Wait for the deployment process.
7. FlutterFlow displays:
   “Deployment Failed – Unknown error. Please contact support@flutterflow.io.”
8. Chrome DevTools shows that the request to tm-prod.dreamflow.cloud/.../run returns HTTP 409.
9. Check Google Cloud > Cloud Build > History.
10. No new Cloud Build execution is created after the deployment attempt.

Reproducible from Blank

• The steps to reproduce above start from a blank project.

Bug Report Code (Required)

IT4wlPHl8Y9Im9tJ0aX2LMAxnjwXIjo3RpIwmu5DQis8GZT0B4kcYs+kfklUOP2oS2xmP0yJhnMX/MqKk/DxCPc7BEicQYg5+rl6VjviJWGgb4imBYS3b3QmHplgCH2M1qWngyVCCM9uW3AC3GaQBtyASj7cQoDqO0Y0D+aoXdeK2SrDX1iXc2URm05KZDPz

Visual documentation

Attached screenshots show:

1. FlutterFlow displaying “Deployment Failed – Unknown error”.
2. Chrome DevTools showing HTTP 409 for the deployment /run request.

3. Google Cloud Build History showing no new build after the deployment attempt.
4. Firebase Blaze plan and active Google Cloud Billing.
5. IAM roles assigned to firebase@flutterflow.io.
6. Cloud Functions Region set to us-central1.

Environment

- FlutterFlow version: FlutterFlow Web Editor, Production version available on July 22, 2026
- Platform: Web
- Browser name and version: Google Chrome 150
- Operating system and version affected: Windows 10

Additional Information

This issue blocks the Push Notifications feature of a delivery application.

Push notifications are required to notify customers when a store accepts an order. The notification action and recipient configuration are already completed in the project, but the feature cannot be tested because the required Firebase Cloud Functions cannot be deployed.

All standard setup checks have already been completed, including Blaze billing, IAM roles, Firestore Rules, Firestore Indexes, us-central1 Cloud Functions Region, Incognito testing, and active Google Cloud Billing.

This appears to fail before Firebase Cloud Build starts, because the FlutterFlow deployment endpoint returns HTTP 409 and no new Cloud Build execution is created.

[Alezanello]

Thanks for your report, So sorry you are experiencing this issue. I was not able to reproduce this on a blank project, but it is replicable on yours. That's why I'm suspecting this is a project-specific issue and our support team is our best chance to get it solved. Do you mind following up with them? You can do that either by email: support@flutterflow.io or using the in-app chat inside of FlutterFlow.

I'm going to close this issue since this tracker is specifically for bugs reproducible from blank projects.

If you were able to reproduce this on a blank project as well, please let us know and provide the bug code of that project.

Thanks so much!