The message (image) received from the pulse always omits data from a specific column. I checked and the column has visibilityeverywhere.
The only thing I can think of is that the field type is description… implying potentially long text. Is the pulse-Slack API unable to handle long text? (In reality the text is usually just a few lines long).
Hi @Yen
Yes, the Description field type will be removed from pulses, since that type is normally used for longer texts, which isn’t suitable for short things like pulses.
You can set the type to “No special type” (bottom) to include it.
UPDATE: Yikes… sorry @flamber but it seems ever since I changed the field from ‘description’ to no special type, the slack pulse interface just spins… it can’t seem to render a pulse at all anymore (not even one without the text column) and nothing at all is sent to slack.
@Yen
Okay, I’m pretty sure you’re hitting this issue (very bad description, scroll down to bottom): https://github.com/metabase/metabase/issues/9891
It’s been given Priority 1, but it hasn’t been scheduled for any milestone yet - the team is busy working on the major query browser overhaul in 0.33
So even if you change the type back to Description, it still doesn’t work?
Do you mean that now all pulses are not working or just this single item?
EDIT: Latest release is 0.32.9 (not that I think it will solve your problem, but just noting it)
I’m gonna go back and check if it’s ALL pulses or just this one… I suspect its just this one - i don’t think we’ve impld any other pulses yet). Will report back.
@Yen Okay, that’s good. But does the failing pulse start working again if you change field type back to Description?
EDIT: I’m trying to see if I can reproduce your problem, since that will help fixing the issue.
Hi @flamber, yes - the failing pulse starts working again when I change the field back to description - but, per the issue that kicked everything off, the description field itself is never rendered.
It is anything that you can type into a slack message. So yes there may be newlines, there MAY be markdown down and emojis but so far I’m not seeing any.
About 75% is a single line comment.
The rest might be a paragraph of text, at most two.
@Yen Okay, I’ve tried multiple different ways to reproduce this without success. I’ve tried to create a varchar(2000) column and populate it with random text and special characters (newline, emoji, etc), but it doesn’t trigger the error. I’ll leave a comment on the issue, and maybe it will help pointing in the right direction.