---
title: "Troubleshooting"
description: "Learn how to troubleshoot your SDK setup."
url: https://docs.sentry.io/platforms/ruby/guides/rails/troubleshooting/
---

# Troubleshooting for Rails

## [General](https://docs.sentry.io/platforms/ruby/guides/rails/troubleshooting.md#general)

Why was my tag value truncated?

Currently, every tag has a maximum character limit of 200 characters. Tags over the 200 character limit will become truncated, losing potentially important information. To retain this data, you can split data over several tags instead.

For example, a 200+ character tagged request:

`https://empowerplant.io/api/0/projects/ep/setup_form/?user_id=314159265358979323846264338327&tracking_id=EasyAsABC123OrSimpleAsDoReMi&product_name=PlantToHumanTranslator&product_id=161803398874989484820458683436563811772030917980576`

The 200+ character request above will become truncated to:

`https://empowerplant.io/api/0/projects/ep/setup_form/?user_id=314159265358979323846264338327&tracking_id=EasyAsABC123OrSimpleAsDoReMi&product_name=PlantToHumanTranslator&product_id=1618033988749894848`

## [Profiling](https://docs.sentry.io/platforms/ruby/guides/rails/troubleshooting.md#profiling)

Why am I not seeing any profiling data?

If you don't see any profiling data in [sentry.io](https://sentry.io), you can try the following:

* Ensure that [Tracing is enabled](https://docs.sentry.io/platforms/ruby/guides/rails/tracing.md).
* Ensure that the automatic instrumentation is sending performance data to Sentry by going to the **Performance** page in [sentry.io](https://sentry.io).
* If the automatic instrumentation is not sending performance data, try using [custom instrumentation](https://docs.sentry.io/platforms/ruby/guides/rails/tracing/instrumentation/custom-instrumentation.md).
* Enable [debug mode](https://docs.sentry.io/platforms/ruby/guides/rails/configuration/options.md#debug) in the SDK and check the logs.

### [Limitations](https://docs.sentry.io/platforms/ruby/guides/rails/troubleshooting.md#limitations)

Profiles for multi-threaded servers like `puma` might not capture frames correctly when async I/O is happening. This is a limitation of `stackprof`.

## [Crons](https://docs.sentry.io/platforms/ruby/guides/rails/troubleshooting.md#crons)

Why aren't recurring job errors showing up on my monitor details page?

You may not have [linked errors to your monitor](https://docs.sentry.io/platforms/ruby/guides/rails/crons.md#connecting-errors-to-cron-monitors).

Why am I not receiving alerts when my monitor fails?

You may not have [set up alerts for your monitor](https://docs.sentry.io/platforms/ruby/guides/rails/crons.md#alerts).

What is the crons data retention policy for check-ins?

Our current data retention policy is 90 days.

What's the shortest schedule a monitor supports?

One minute. Monitor schedules support:

* **Crontab:** Five-field expressions, such as `* * * * *` to run every minute. Six- and seven-field expressions, which add seconds or years, aren't supported.
* **Interval:** Units of `minute`, `hour`, `day`, `week`, `month`, or `year`. There's no `second` unit.

Sentry can't create or update a monitor for a job that runs more than once a minute, such as every 10 or 30 seconds.