block_reason: OTHER

Description of the bug:

Hi,
I'm using gemini-pro to generate user preferences based on user reviews. However, I encountered an issue when my prompt was flagged and blocked due to the reason: other. Upon reviewing the content, I noticed it was a movie review that contained words such as "rapped," "toilet humor," etc. I'm currently unable to proceed further from this point. How can I resolve this issue?

Thank you.

Actual vs expected behavior:

No response

Any other information you'd like to share?

No response

did you try this safety setting:

safety_settings = [ {"category": "HARM_CATEGORY_HARASSMENT", "threshold": "BLOCK_NONE"}, {"category": "HARM_CATEGORY_HATE_SPEECH", "threshold": "BLOCK_NONE"}, {"category": "HARM_CATEGORY_SEXUALLY_EXPLICIT", "threshold": "BLOCK_NONE"}, {"category": "HARM_CATEGORY_DANGEROUS_CONTENT", "threshold": "BLOCK_NONE"}, ]

Yes I did. Still I am getting the block_reason:OTHER output. Let me give you the specific user review for which I am getting this output:

This will probably end up as a cult classic, but it's pure trash. It is based on a clever idea (making a documentary in America for the benefit of Kasakhstan) and the Borat character is charming, but there is too much toilet humor here. There are several jokes about rape, which is not the least bit funny, especially for anyone who has ever been raped. It's a vulgar movie that should be "X" rated. It tries to be funny, but it tries too hard and goes to the gutter too often for laughs. Probably immature 16-years old guys will find this movie a real hoot. I thought it was a stupid movie with not much to redeem it. It could have really been a great movie as the premise was good (not understanding cultural differences between two countries and the sticky situations that come about as a result). Unfortunately, it just doesn't work. There are some moments that should be funny, such as when Borat invites a chubby black prostitute to a totally white high society dinner party. I did laugh when Borat goes to buy a pet for protection and ends up with a bear. Don't waste your time. There are lots funnier movies, but maybe this was not intended to be a comedy. It's certainly not a serious movie

Any assistance in resolving this issue would be appreciated.

Yes I did. Still I am getting the block_reason:OTHER output.

Same issue for me

I have same issue. Any workaround? Thanks

When utilizing gemini-pro-vision to deal with domainnet/sketch/toe/sketch_314_000022.jpg (an image from Domainnet dataset), I met the same issue. How can I solve this? Thanks!

Any updates on this??

Extremely annoying and I have no idea how to resolve this!

Yeah This is so annoying, it's like Google enforcing it's agenda despite everything is set to NONE

@dipakmeher

Hi, sorry there are some filters that we just can't turn off, these all go into the "OTHER" finish reason.

For example: one of the non-configurable filters is child safety, which is a legal requirement.

@dipakmeher - your example seems to be flagged because it includes both "rape" and "16-years-old".

@MarkDaoust

@MarkDaoust, thank you for addressing this issue. I am using Gemini Pro to generate user preferences based on their movie reviews. Is there a way to proceed with such tasks and reviews since they are genuine reviews on the movies?

Wow, then why give users the illusion of choice. Looks like turning Block Reason to none is next to useless.

@dipakmeher

@dipakmeher - I sent that to the owners as an example of a false positive. Thanks for reporting.

I had the same problem when submitting an analysis and classification of a video related to an advertisement for baby diapers. My application aims to identify the advertiser and the brand of the advertisement.

i have this issue today with api gemini-exp-1206

block_reason: OTHER

no specific error reason how to trace??

How can I resolve this restriction? My IP address is located in the USA.

me too

same issue

Mine was a VPN issue, and I've resolved it. 发自移动版 Gmail

…

On Wed, Feb 5, 2025 at 09:10 zzc0208 ***@***.***> wrote: same issue — Reply to this email directly, view it on GitHub <#276 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFQYN7O4236R32VGJJUSCYD2OFQJZAVCNFSM6AAAAABGBPCOQ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZVGQ4DCMRVHA> . You are receiving this because you commented.Message ID: ***@***.***>

Same here, please add more meaningful api response.

I got this on aistudio and thought I had overused it but nah the prompt was simply an AI assistant trying to present the app maybe it sounded too commercial. Love the aistudio results tho.

@MarkDaoust

@MarkDaoust can you please have a look at this text to help me understand why it would trigger the safety settings:

[happily] Je vais répéter la phrase, dans trois... deux... un... [inhales deeply] La phrase, c'est "[very slowly for emphasis] Mais il y a plein d'autres choses que vous pouvez dire, d'autres mots, d'autres expressions pour féliciter une personne, n'est-ce pas, en français". [inhales deeply] Cette phrase veut dire "[English explanation] But there are plenty of other things you can say, other words, other expressions to congratulate someone, right, in French". [inhales deeply] Les verbes utilisés ici sont "il y a" qui est conjugué de "avoir" qui signifie "[English explanation] there is or there are", "pouvez" qui est conjugué de "pouvoir" qui signifie "[English explanation] to be able to; can", "dire" qui est conjugué de "dire" qui signifie "[English explanation] to say", "féliciter" qui est conjugué de "féliciter" qui signifie "[English explanation] to congratulate" et "est" qui est conjugué de "être" qui signifie "[English explanation] to be (used in tag question)".  [inhales deeply] Ensuite, voici des autres mots que vous devez connaître: "plein" signifie "[English explanation] plenty of; a lot of". "autres" signifie "[English explanation] other". "choses" signifie "[English explanation] things". "mots" signifie "[English explanation] words". "expressions" signifie "[English explanation] expressions; set phrases". "personne" signifie "[English explanation] person; someone". "français" signifie "[English explanation] French (language)". [inhales deeply] Enfin, il y a aussi des expressions idiomatiques que vous devez connaître: "n'est-ce pas" est une expression idiomatique qui veut littéralement dire "[English explanation] isn't it?". Dans ce contexte, cela exprime l'idée de "[English explanation] right? (tag question asking for confirmation)" en anglais. "plein de" est une expression idiomatique qui veut littéralement dire "[English explanation] full of". Dans ce contexte, cela exprime l'idée de "[English explanation] a lot of; plenty of" en anglais. [inhales deeply] Et maintenant, passons à la phrase suivante.

It's a script that I'm trying to generate audio for, and it's a mix of French and English.

@CodeWithOz

Hi @CodeWithOz

https://colab.research.google.com/drive/1vEicabqPU3N_yibNJTmBgIampEF_9wdj

That text TTS's just fine. I don't think there's any problem with the content.

Facing same issue block_reason: OTHER while generating some conversation attached with some doc and in the call there is no abusive word.

Same issue. All block settings set to NONE. Getting block_reason: other for innocuous property record documents.

private const SAFETY_SETTINGS = [
        ['category' => 'HARM_CATEGORY_HARASSMENT', 'threshold' => 'BLOCK_NONE'],
        ['category' => 'HARM_CATEGORY_HATE_SPEECH', 'threshold' => 'BLOCK_NONE'],
        ['category' => 'HARM_CATEGORY_SEXUALLY_EXPLICIT', 'threshold' => 'BLOCK_NONE'],
        ['category' => 'HARM_CATEGORY_DANGEROUS_CONTENT', 'threshold' => 'BLOCK_NONE'],
    ];

Navigation Menu

Repository navigation

block_reason: OTHER #276

Description of the bug:

Actual vs expected behavior:

Any other information you'd like to share?

13 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

block_reason: OTHER #276

Description

Description of the bug:

Actual vs expected behavior:

Any other information you'd like to share?

Activity

Andy963 commented on Apr 11, 2024

dipakmeher commented on Apr 11, 2024

ArunJRK commented on Apr 15, 2024

pribadihcr commented on Apr 16, 2024

anomous123 commented on Apr 18, 2024

tawsifkamal commented on Apr 21, 2024

caliburn420 commented on Apr 22, 2024

MarkDaoust commented on Apr 22, 2024

dipakmeher commented on Apr 22, 2024

caliburn420 commented on Apr 22, 2024

MarkDaoust commented on Apr 23, 2024

13 remaining items

dfvalentim commented on Sep 16, 2024

s9anus98a commented on Dec 16, 2024

TianhuaJu commented on Jan 10, 2025

zsan3653 commented on Jan 10, 2025

zzc0721 commented on Feb 5, 2025

TianhuaJu commented on Feb 5, 2025

Somebi commented on Feb 28, 2025

asasvirtuais commented on May 27, 2025

CodeWithOz commented on Nov 2, 2025

MarkDaoust commented on Nov 3, 2025

samir-lawsikho commented on Dec 10, 2025

sblawrie commented on Dec 16, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions