# Troubleshooting and Support

This section covers some common issues you might run into while working with UDFs, along with practical steps to troubleshoot and get things back on track.

## **Common Issues and Fixes**

1. **Filter Configuration Issues**
   * **Problem**: The UDF isn’t capturing the expected data.
   * **Fix**: Double-check your `get_filter job` setup. Make sure it includes the conditions needed to capture the right data. Confirm that field names and values match what’s actually in the data source.
2. **Data Collection or Processing Errors**
   * **Problem**: Data isn’t saving to the database, or unexpected data is showing up in the logs.
   * **Fix**: Look at the `_collect` and `_process` functions to ensure they’re running in sequence. Check that data transformations in `_process` are working as expected, and verify that any dependency data is correctly fetched and formatted.
3. **Slow or Failing Dependency Data Acquisition**
   * **Problem**: The UDF is slow or failing when pulling dependency data.
   * **Fix**: Review your data acquisition setup and consider simplifying it with the standardized collection methods. Only fetch the data you absolutely need to keep things efficient.
4. **Database Model Conflicts**
   * **Problem**: Errors related to storing data in the database or issues with schema conflicts.
   * **Fix**: Confirm that all hex fields are set to store as `bytea` in your model. Make sure fields like `address` or `transaction_hash` (reserved fields) are only used as intended to avoid conflicts.
5. **Hex and String Conversion Errors**
   * **Problem**: Errors related to data format, especially with hex-string conversions.
   * **Fix**: Use the utility methods designed for hex and string conversions, especially when working with blockchain addresses and transaction hashes, to keep data consistent and avoid format issues.

## **Getting Help and Giving Feedback**

If you’ve tried these fixes but still have trouble, or if you think you’ve found a unique issue, here’s what you can do:

1. **Document Your Steps**: Take note of what you’ve tried, any error logs, and relevant configurations.
2. **Reach Out for Help**: You can open a GitHub issue or email <contact@thehemera.com> or reach us out on [discord](https://discord.gg/socialscan). Including as much detail as possible will make it easier for the team to help you quickly.