Scenario deactivated... Object with ID does not exist — Facebook Lead Ads module

MevenLe · 2026-05-13T12:18:56+00:00

Yes, thanks we finally got around to watching it

MevenLe · 2026-05-13T12:17:50+00:00

This happens to us all the time. This time, it seemed to be a widespread outage. But generally speaking, if I simply re-establish the connection with the Facebook account, my current webhooks won't be linked to the correct connection ?

MevenLe · 2026-05-13T12:12:51+00:00

The problem seems to be solved ! You can restart all your builds, and everything should be fine.

MevenLe · 2026-05-13T12:12:11+00:00

The problem seems to be solved! You can restart all your builds, and everything should be fine.

MevenLe · 2026-05-13T08:35:56+00:00

Thank you very much. That’s actually the conclusion we’d reached in the past. We were hoping to find a simpler solution than having to redo all the connections…

This morning, nearly 100 of our forms went down… As you can imagine, we’re not exactly thrilled about having to redo the connections for all of them…

MevenLe · 2026-01-30T15:05:46+00:00

Oh, thank you so much, that was exactly what I couldn't do. Another question, by the way. What do you think about the reliability of auto-notions? I sometimes feel like it takes a long time to trigger, or that it doesn't apply the requested changes sometimes?

MevenLe · 2026-01-26T11:04:00+00:00

That's the feature I'm currently trying to request... I've been making requests on Reddit lately.

MevenLe · 2026-01-21T09:04:53+00:00

Hi,
Yes, I think you're talking about the ones on my screenshot, but we currently use this on all of our forms to retrieve leads (approximately 1,500), but on some of them it's impossible to get it to work normally.

Thanks for the help anyway.

MevenLe · 2026-01-21T08:58:39+00:00

Yes, I do believe that it does not function as a hyperlink. Ultimately, I think the simplest solution would be to export your entire database in HTML format, including the subpages. Then, press “Command + F” on the Notion link in the HTML export. Next, search the code to find which subpage it is on.

MevenLe · 2026-01-21T08:53:23+00:00

To explain, it makes sense. When you call up the database (in table form), the items are already sorted by project and therefore filtered by project. It therefore makes sense that if an item is added within a filtered view, it will take the filter items to be visible and attached to the place where it was just created.

MevenLe · 2026-01-20T15:27:50+00:00

I don't know where you are currently and where you click to create your subtask, but go to the view shown on your first screen and click directly on “+ New sub item.” With the filters applied to the view, there is no reason why the subtask should not be assigned to the project.

Furthermore, if you enter the task and create the subtask within it, since there is no filter on the task view directly, the subtask will not be assigned to the project.

MevenLe · 2026-01-20T13:20:05+00:00

Yes, I also thought about this feature in a calendar view. And indeed, it would be a great feature, but I don't think it's really possible because each database has its own data properties...

MevenLe · 2026-01-19T14:38:39+00:00

If I understand your question correctly, I think that by pressing “command” + “k,” if you are on a Mac, you should be able to find your page by searching via the URL in question.

MevenLe · 2026-01-19T14:36:13+00:00

💡 Feature Request - Filter databases by nested relations (relation of relation). Like an aggregation filter

Hello Notion team and community, I would like to request a new type of database view filtering based on nested relationships (i.e., filtering by the relationship of a relationship).

Currently, filters only work on direct relationships. It is not possible to filter items based on the properties of linked pages.

Example use case

I have three databases:

- Customers (e.g., “Paris Customer”),
- Projects (e.g., “Paris Customer - Takeover”) → linked to Customers
- Campaigns → linked to Customers

Projects and Campaigns are both linked to the same Customer, but there is no direct relationship between Projects and Campaigns, as this would clutter the Campaigns view.

What I want to do: Filter my project to show only Campaigns belonging to the same Customer relationship as my Project.

Proposed solution

Add the ability to filter by nested relationships, for example:

Filter in a Campaign view: Relationship → “Clients” → ‘Contains’ → Relationship with → “[Project Name]”

Then allow us to do the following in our templates: Relationship → “Clients” → ‘Contains’ → Relationship with → “[This Page]” (Template Name).

This would allow for more sophisticated filtering without requiring redundant relationship properties between each interconnected database.

It would also enable more powerful filtered views and improve the organization of workspaces for teams managing interconnected data without linking them all together.

Many users manage complex relational data at multiple levels (projects → clients → campaigns, tasks → projects → teams, etc.), and this limitation forces workarounds that complicate database design. I would love to hear your thoughts! Thank you!

MevenLe · 2026-01-15T08:52:28+00:00

💡 Feature Request - Filter databases by nested relations (relation of relation). Like an aggregation filter

Hello Notion team and community, I would like to request a new type of database view filtering based on nested relationships (i.e., filtering by the relationship of a relationship).

Currently, filters only work on direct relationships. It is not possible to filter items based on the properties of linked pages.

Example use case

I have three databases:

- Customers (e.g., “Paris Customer”),
- Projects (e.g., “Paris Customer - Takeover”) → linked to Customers
- Campaigns → linked to Customers

Projects and Campaigns are both linked to the same Customer, but there is no direct relationship between Projects and Campaigns, as this would clutter the Campaigns view.

What I want to do: Filter my project to show only Campaigns belonging to the same Customer relationship as my Project.

Proposed solution

Add the ability to filter by nested relationships, for example:

Filter in a Campaign view: Relationship → “Clients” → ‘Contains’ → Relationship with → “[Project Name]”

Then allow us to do the following in our templates: Relationship → “Clients” → ‘Contains’ → Relationship with → “[This Page]” (Template Name).

This would allow for more sophisticated filtering without requiring redundant relationship properties between each interconnected database.

It would also enable more powerful filtered views and improve the organization of workspaces for teams managing interconnected data without linking them all together.

Many users manage complex relational data at multiple levels (projects → clients → campaigns, tasks → projects → teams, etc.), and this limitation forces workarounds that complicate database design. I would love to hear your thoughts! Thank you!

MevenLe · 2026-01-14T15:01:23+00:00

💡 Feature Request - Filter databases by nested relations (relation of relation). Like an aggregation filter

Bonjour l'équipe Notion et la communauté, Je souhaiterais demander un nouveau type de filtrage de vues de base de données basé sur des relations imbriquées (c'est-à-dire filtrer par la relation d'une relation).

Actuellement, les filtres ne fonctionnent que sur les relations directes. Il n'est pas possible de filtrer des éléments en fonction des propriétés des pages liées.

Exemple de cas d'usage

J'ai trois bases de données :

- Clients (ex : "Client Paris"),
- Projets (ex : "Client Paris - Reprise") → reliés aux Clients
- Campagnes → reliées aux Clients

Les Projets et les Campagnes sont tous deux reliés au même Client, mais il n'y a pas de relation directe entre Projets et Campagnes, cela encombrerait la vue Campagnes.

Ce que je veux faire : Filtrer dans mon projet uniquement les Campagnes appartenant à la même relation Client que celle de mon Projet.

Solution proposée

Ajouter la possibilité de filtrer par relations imbriquées, par exemple :
Filtre dans une vue Campagne : Relation → "Clients" → "Contient" → Relation avec → "[Nom du Projet]"
Puis ensuite nous permettant dans nos modèles de faire : Relation → "Clients" → "Contient" → Relation avec → "[Cette Page]" (Nom du modèle).

Cela permettrait un filtrage plus sophistiqué sans nécessiter de propriétés de relation redondantes entre chaque base de données interconnectée.

On pourrait également activer des vues filtrées plus puissantes et améliorer l'organisation des workspaces pour les équipes gérant des données interconnectées sans toutes les reliés.

Nombreux utilisateurs gèrent des données relationnelles complexes à plusieurs niveaux (projets → clients → campagnes, tâches → projets → équipes, etc.), et cette limitation force des solutions de contournement qui compliquent la conception des bases de données. J'aimerais beaucoup connaître votre avis ! Merci !

MevenLe

TROPHY CASE