-
-
Notifications
You must be signed in to change notification settings - Fork 720
Description
Describe the bug (I dont know its bug or no)
I use some iFlow's auth on my proxy. But I always see
[2025-12-31 18:53:15] [--------] [info ] [service.go:577] file watcher started for config and auth directory changes
[2025-12-31 18:53:15] [--------] [info ] [service.go:583] core auth auto-refresh started (interval=15m0s)
[2025-12-31 18:53:15] [--------] [error] [iflow_executor.go:368] iflow executor: token refresh failed: iflow token: missing access token in response
[2025-12-31 18:53:15] [--------] [error] [iflow_executor.go:368] iflow executor: token refresh failed: iflow token: missing access token in response
[2025-12-31 18:53:15] [--------] [error] [iflow_executor.go:368] iflow executor: token refresh failed: iflow token: missing access token in response
[2025-12-31 18:53:15] [--------] [error] [iflow_executor.go:368] iflow executor: token refresh failed: iflow token: missing access token in response
[2025-12-31 18:53:15] [--------] [error] [iflow_executor.go:368] iflow executor: token refresh failed: iflow token: missing access token in response
[2025-12-31 18:53:15] [--------] [error] [iflow_executor.go:368] iflow executor: token refresh failed: iflow token: missing access token in response
[2025-12-31 18:53:15] [--------] [error] [iflow_executor.go:368] iflow executor: token refresh failed: iflow token: missing access token in response
Model Name
All models from iFlow
LLM Client
Droid CLI
Expected behavior
Is this an error warning for iflow? because it can't refresh the token? and there shouldn't be this warning in the terminal?