Hila Kashai
Merged in a post:
To trigger Automations upon related entity deletion and mirror property updates
Isuri Ranawaka
Today, Port Automations will not be triggered upon deleting related entities or updating the value of a mirror property of an entity. But it would be beneficial if it were possible.
Damian Chelverajan.
Another similar customer use case:
When a related entity is deleted, there is no reliable, scalable mechanism to find and update all entities that held a relation to the deleted entity (potentially 2,000+).
Current limitations include:
Bulk upsert API is capped at 20 entities per call with no looping support in automations. The Migrations API only allows one migration per blueprint at a time, making concurrent deletion events unreliable.
Desired outcome: A platform-native mechanism to:
Trigger on a related entity deletion event.
Identify and update all entities holding a relation to the deleted entity at scale (2,000+). Handle concurrent deletion events reliably (e.g., queued migrations or back-pressured automation runs).
Customer impact: blocking reliable use of persistent calculation properties with the Aikido Ocean integration.