Troubleshooting

This page provides a list of common errors that developers may face while building integrations.

Authentication Timeout

Retry the login process (authentication timeout is set to 5 minutes).

boltic login

Connection issues

Check your network connectivity by pinging Boltic:
```
ping console.fynd.com
```
If unsuccessful, check network configurations, firewalls, or proxy settings.

Authentication Failures

If you’re facing authentication issues, try the following:

Errors while Creating Integration

If you’re unable to create an integration, verify the following:

All mandatory fields are completed correctly
Make sure that the icon is valid and properly formatted. You must provide the icon in SVG format.
You’ve selected a valid integration type from the supported options

Authentication Issue

If you're experiencing issues related to authentication, such as failing login or invalid credentials:

Remove cached credentials and tokens by logging out:
```
boltic logout
```
Login again to re-establish your connection and complete the authentication flow in your browser.
```
boltic login
```
Confirm your system can reach the Boltic servers:
```
ping console.fynd.com
```
If this command fails, ensure your internet connection is stable, and no firewall or network configurations are blocking the connection.

Sync Issues

If you're experiencing problems with syncing integrations:

Run the following command toverify the current state of your integration and ensure no errors or warnings are reported:
```
boltic integration status
```

Run the following command to manually trigger synchronization of your integration and verify integration functionality afterward:
```
boltic integration sync
```

Network Issues

If Boltic CLI cannot communicate with the Boltic servers, follow these steps:

Run the following command to confirm that your network can reach Boltic servers:
```
ping console.fynd.com
```
If unsuccessful, check network configurations, firewalls, or proxy settings.

Run the following command to ensure the Boltic API is responding and operational:
```
boltic integration status
```
If API status reports downtime or errors, check the Boltic status page or contact support.

Run the following command to enable detailed log for diagnosing connection or API issues:
```
boltic --verbose integration sync
```
Analyze output carefully to identify potential network or API errors.

Debug Mode

Boltic CLI supports a verbose output mode to help you debug issues efficiently:

Run the following command to debug integration issues, enable verbose log to gain detailed insights:
```
boltic --verbose integration sync
```

Run the following command to apply verbose logging mode to any Boltic command for detailed diagnostic output:
```
boltic --verbose integration create
```
Verbose output is useful to clearly understand the sequence of events and diagnose detailed integration issues.

If you need further assistance, use Boltic CLI’s built-in help commands: