Azure functions offline after deployment

[danny8002]

Investigative information

Please provide the following:

• Timestamp: 2019-04-09 08:00:00.567Z
• Function App version (1.0 or 2.0): 2.0
• Function App name: satoriportalfuncs
• Function name(s) (as appropriate): all of the functions under the app
• Invocation ID:
• Region: WestUS2

Repro steps

1. 2019-04-09 08:00:00.567Z, I deploy the function app from VS code with 'Azure Functions' plugin.
2. after the deployment finished, i found the functions stopped
3. I click 'Run' of functions, it show 'internal server error'
4. I try to find the log under https://satoriportalfuncs.scm.azurewebsites.net/DebugConsole, no any error message. only a few text show the status=Offline
5. about 4 hours later, i restart the app, it works now

this is the last invoke before deployment
Executing 'Functions.SyncFromXXXXXXXTimer' (Reason='Timer fired at 2019-04-09T08:00:00.5673343+00:00', Id=84be2452-8ee4-449d-929f-5d5801c77419)

after restart about 4 hours later
Executing 'Functions.SyncFromXXXXXXXTime' (Reason='Timer fired at 2019-04-09T12:04:13.0300220+00:00', Id=e061eede-3a1a-41e1-93d9-ba91f4394650)

Expected behavior

I always use VS code to do deployment and this works well before this deployment.

Actual behavior

after deployment, the function app stops.

Known workarounds

restart

Related information

Provide any related information

• Programming language used (Javascript/Node)

• Links to source (see the App)
  depoyment.log.from.vscode.txt

• Bindings used (CosmosDb )

[sylvaingirardbe]

Sounds a lot like #4275. Can you check in the monitor section of the function and look at the invocation details of a failed call?

[pragnagopa]

@danny8002 - Does this issue repro consistently?

[sylvaingirardbe]

FWIW, in my case it wasn't reproducible, happened at least once, maybe twice, not sure about the first time. It was a deploy from within VS Code every time. I set up a DevOps CI/CD pipeline yesterday and did 10 to 20 deploys and all went fine.

[danny8002]

@danny8002 - Does this issue repro consistently?

no, just happens once.

[pragnagopa]

Closing due to inactivity.