Error publishing/deploying Shiny App, worked before, now doesn't

publication

#1

I have a Shiny App (Interactive Document) deployed to shinyapps.io that has worked fine until now. After a minor update to the code, when I try to publish I am now getting a HTTP 599: Timeout error. The app appears on shinyapps.io flagged as "Undeployed". Publishing under a new name did not help. Here is the verbose deploy log:

...
[2018-03-26T00:50:20.178259556+0000] Copying file packrat/desc/geosphere
[2018-03-26T00:50:20.180903283+0000] Copying file packrat/desc/stringi
GET /v1/tasks/?filter=account_id:102456&filter=parent_id:516078380&count=100&offset=0 829ms
################################# End Task Log ################################# 
----- Deployment error -----
Error: Unhandled Exception: Child Task 516078380 error: Unhandled Exception: HTTP 599: Timeout
 
----- Error stack trace -----
3: stop(status$error, call. = FALSE)
2: client$waitForTask(taskId, quiet)
1: rsconnect::deployApp(appDir = "~/Projects/Pasture_Potential/bopsoil", 
       appFileManifest = "C:/Users/WOODWA~1/AppData/Local/Temp/7e0d-7903-b5ac-c3d6", 
       appPrimaryDoc = "pasture9.rmd", appSourceDoc = "~/Projects/Pasture_Potential/bopsoil/pasture9.rmd", 
       account = "woodward-dairynz", server = "shinyapps.io", appName = "pasture9", 
       appId = 307875, launch.browser = function(url) {
           message("Deployment completed: ", url)
       }, lint = FALSE, metadata = list(asMultiple = FALSE, asStatic = FALSE), 
       logLevel = "verbose")
Error: Unhandled Exception: Child Task 516078380 error: Unhandled Exception: HTTP 599: Timeout
Execution halted

#2

Additional information:

R version 3.4.4 (2018-03-15) -- "Someone to Lean On"
Copyright (C) 2018 The R Foundation for Statistical Computing
Platform: i386-w64-mingw32/i386 (32-bit)

Windows 10.

All packages up to date except lubridate (latest version won't compile, have latest compiled version)


#3

Huh, and now it's working. This makes me wonder if it was a temporary slow down of our local network that caused the timeout, or maybe something at the shinyapps.io end that is now resolved.


#4

Hi,
If it's resolved (even by your own wizardry— or turning it on and off), would you mind selecting a solution?