Troubleshooting

A compilation of common problems and their solutions. Please use this to help resolve issues.

Common Issues

Workflow execution fails

Main causes and solutions when errors occur during workflow execution.

1. Check block connections

Please check that all blocks are properly connected:

  • • Input block → Process block → Output block sequence
  • • Connection lines are properly drawn
  • • No isolated blocks exist

2. External service authentication status

External service integration blocks such as Gmail and Slack require authentication:

  • • Check authentication status in each block's settings screen
  • • Re-authenticate if necessary
  • • Access permissions are properly configured

3. Block configuration verification

Please check the configuration content of each block:

  • • All required fields are filled in
  • • Input values are in the correct format (email addresses, URLs, etc.)
  • • Settings are within character limits

Basic solutions to try first

  • Refresh browser (F5 or Cmd+R) and re-execute workflow
  • Check workflow save status (save before execution if unsaved)
  • Confirm internet connection is stable
  • Confirm external services (Gmail, Slack, etc.) are operating normally

Cannot authenticate Gmail

Solutions for when Gmail block authentication errors occur.

Common error messages:

"Error 403: access_denied"

"Error 400: redirect_uri_mismatch"

"Authentication error occurred"

Resolution steps:

  1. Clear browser cache and cookies
  2. Open Gmail block settings screen
  3. Click 'Gmail Authentication' button to re-authenticate
  4. Select appropriate account on Google authentication screen
  5. Grant all required permissions (Gmail read/send)
  6. After authentication completes, return to settings screen and confirm connection status

Slack message sending error

Solutions for when Slack block message sending fails. Supports both OAuth and Webhook authentication.

Common check items:

For OAuth authentication:
  • Confirm Slack authentication is completed
  • Enter channel name without # (e.g.: general)
  • nanocraft app is added to the channel
For Webhook authentication:
  • SLACK_WEBHOOK_URL is set in environment variables
  • Channel name is entered correctly

Recommended procedure:

Use the 'Test Send' button in the Slack block settings screen to verify settings beforehand. Also, when using OAuth authentication, please select the appropriate channel from the channel list.

Cannot process audio files

Solutions for when audio input block file processing fails.

Supported file formats:

  • • MP3, WAV, M4A, OGG, WebM, AAC
  • • File size: Within 25MB (Groq API limitation)
  • • Recognition accuracy may decrease if audio is not clear

When errors occur:

  1. Check file format and size
  2. Check if audio file is not corrupted
  3. Try with a different audio file
  4. Re-encode file with conversion software

Common Error Messages

Gmail Authentication Error

"Error 403: access_denied"

"Error 400: redirect_uri_mismatch"

"Authentication processing error"

Google account permission approval is not completed or there is an issue with OAuth settings. Please restart Gmail authentication from the beginning.

Slack Sending Error

"channel_not_found"

The specified channel does not exist or the nanocraft app is not added to the channel.

Audio Processing Error

"Invalid file format"

Unsupported file format. Please convert to one of MP3, WAV, M4A, OGG, WebM, AAC.

AI Processing Error

"Speech recognition timed out"

File size is too large or processing time is too long. Please split the file into smaller parts and try again.

If the problem is not resolved

If the problem cannot be resolved with the above methods, please let us know the detailed situation

Contact Support Contact by Email