https://community.esri.com/t5/geoprocessing-questions/unintended-external-triggers-on-public/m-p/1697213#M27723 <P>We have several public-facing geoprocessing services that allow our application to send emails when certain events are triggered. These services have been running for years without any issues. Recently, however, they’ve started being triggered from outside the application, and the services are running with default parameters. Our initial suspicion is that bots are hitting the service URLs. Has anyone experienced something similar recently or have suggestions on how to obscure or protect the URLs while still allowing the application to access them?</P> Mon, 20 Apr 2026 13:44:40 GMT JennaWalz3 2026-04-20T13:44:40Z https://community.esri.com/t5/geoprocessing-questions/unintended-external-triggers-on-public/m-p/1697213#M27723 <P>We have several public-facing geoprocessing services that allow our application to send emails when certain events are triggered. These services have been running for years without any issues. Recently, however, they’ve started being triggered from outside the application, and the services are running with default parameters. Our initial suspicion is that bots are hitting the service URLs. Has anyone experienced something similar recently or have suggestions on how to obscure or protect the URLs while still allowing the application to access them?</P> Mon, 20 Apr 2026 13:44:40 GMT https://community.esri.com/t5/geoprocessing-questions/unintended-external-triggers-on-public/m-p/1697213#M27723 JennaWalz3 2026-04-20T13:44:40Z