Azure App Service es un servicio que se usa para crear e implementar aplicaciones web críticas escalables.
Azure App Service ETL stopped updating SQL after 2026-04-02; Power Automate calls return HTTP 200 but ProjectProfitabilityArchive / ProcoreRefreshTimes no longer advance
We have an integration that loads Procore profitability data into Azure SQL (tables include dbo.ProjectProfitabilityArchive and dbo.ProcoreRefreshTimes). The last successful snapshot in the database is 2026-04-02 (e.g. MAX(ArchiveDate) and MAX(RefreshTime) both stop on that date).
Downstream: our internal app (Bolt) and Power BI both read the same database, so both show data only as of 2026-04-02.
Orchestration: Power Automate cloud flows (ProcoreRefresh Daily Automatic and Procore Refresh PM) still run on schedule and report success. The first step is an HTTP GET to https://tatcoprocoreetl.azurewebsites.net/etl/etl which returns HTTP 200 with a JSON body like {"status":200,"message":"Successful"}, but SQL does not receive new rows after 2026-04-02.
Need help with: identifying why the App Service (or related pipeline) is not writing to Azure SQL anymore—whether the endpoint is a no-op, misconfigured, failing internally, or blocked by auth/connection strings/credentials—and what to check in App Service logs, Application Insights, and configuration to restore the load.
Environment (if useful): Azure subscription active; resources include Data Factory tatcodatafactory, SQL database, and App Service–style hosting for the ETL URL above.