You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have seen cases where the loader is configured with the wrong password for the warehouse. The initialization results in an exception, and the loader crashes. The orchestration continually restarts the app, and it crashes every time. Eventually the user gets temporarily locked out of the warehouse because of so many password failures.
Instead of crashing, it would be better to surround the initialization in a retry block with exponential backoff. As long as we back off sufficiently, then connection attempts will be infrequent and the user would not get locked out of the warehouse.
The text was updated successfully, but these errors were encountered:
Currently, the loader runs some initialization when it first starts up.
We have seen cases where the loader is configured with the wrong password for the warehouse. The initialization results in an exception, and the loader crashes. The orchestration continually restarts the app, and it crashes every time. Eventually the user gets temporarily locked out of the warehouse because of so many password failures.
Instead of crashing, it would be better to surround the initialization in a retry block with exponential backoff. As long as we back off sufficiently, then connection attempts will be infrequent and the user would not get locked out of the warehouse.
The text was updated successfully, but these errors were encountered: