Bug ID Number |
BUG-000164278 |
Submitted | January 11, 2024 |
Last Modified | September 9, 2024 |
Applies to | ArcGIS Online |
Version found | Oct 2023 |
Operating System | N/A |
Operating System Version | N/A |
Status | As Designed
After review by the development team, it has been determined that this behavior is as designed. See the Additional Information section for details.
|
Additional Information
When listening to trigger on a feature layer, the trigger must always be followed by the 'Fetch updates, changes,...' action in the flow. Within this 'Fetch update...' action, re-confirm the the sub-layer in the feature service that is of interest which was already selected when configuring the trigger. Though the flow is triggered when a feature is created in any of the sub-layers, it does not run beyond the 'Fetch updates, changes,....' if it's not the interested layer.
Workaround
Split the two sublayers into two separate feature layers. Republishing the point and polygon layers as separate hosted feature layers does not return this error.
Steps to Reproduce