Pulse failing 0.34.2

A Pulse that I have setup to run weekly failed this week after updating to 0.34.2 last week.
The associated questions do not load when viewing the Pulse.
Nor do they load when attempting to create a new Pulse.
However, they run and load normally outside of Pulse.

Hi @bpho
Which version did you upgrade from?
Please post “Diagnostic Info” from Admin > Troubleshooting.
And could you also check the log for any errors that might be happening, when it fails to load? Admin > Troubleshooting > Logs

Hi @flamber

Upgraded from 0.33.6
Pertinent log below:
GET /api/pulse/preview_card_info/543 500 5.9 s (12 DB calls)
{:message “Unrecognized token ‘E’: was expecting (‘true’, ‘false’ or ‘null’)\n at [Source: (StringReader); line: 1, column: 2]”,
:type com.fasterxml.jackson.core.JsonParseException,
:stacktrace
(“com.fasterxml.jackson.core.JsonParser._constructError(JsonParser.java:1804)”
“com.fasterxml.jackson.core.base.ParserMinimalBase._reportError(ParserMinimalBase.java:679)”
“com.fasterxml.jackson.core.json.ReaderBasedJsonParser._reportInvalidToken(ReaderBasedJsonParser.java:2835)”
“com.fasterxml.jackson.core.json.ReaderBasedJsonParser._handleOddValue(ReaderBasedJsonParser.java:1889)”
“com.fasterxml.jackson.core.json.ReaderBasedJsonParser.nextToken(ReaderBasedJsonParser.java:747)”
“cheshire.parse$parse.invokeStatic(parse.clj:88)”
“cheshire.parse$parse.invoke(parse.clj:86)”
“cheshire.core$parse_string.invokeStatic(core.clj:206)”
“cheshire.core$parse_string.invoke(core.clj:192)”
“cheshire.core$parse_string.invokeStatic(core.clj:202)”
“cheshire.core$parse_string.invoke(core.clj:192)”
“clojure.core$comp$fn__5807.invoke(core.clj:2569)”
“clojure.core$comp$fn__5807.invoke(core.clj:2569)”
“medley.core$map_keys$fn__1762$fn__1763.invoke(core.cljc:89)”
“clojure.core$fn__8429$fn__8431.invoke(core.clj:6840)”
“clojure.core.protocols$iter_reduce.invokeStatic(protocols.clj:49)”
“clojure.core.protocols$fn__8140.invokeStatic(protocols.clj:75)”
“clojure.core.protocols$fn__8140.invoke(protocols.clj:75)”
“clojure.core.protocols$fn__8088$G__8083__8101.invoke(protocols.clj:13)”
“clojure.core$reduce.invokeStatic(core.clj:6828)”
“clojure.core$fn__8429.invokeStatic(core.clj:6830)”
“clojure.core$fn__8429.invoke(core.clj:6830)”
“clojure.core.protocols$fn__8167$G__8162__8176.invoke(protocols.clj:175)”
“clojure.core$reduce_kv.invokeStatic(core.clj:6856)”
“clojure.core$reduce_kv.invoke(core.clj:6847)”
“medley.core$reduce_map.invokeStatic(core.cljc:70)”
“medley.core$reduce_map.invoke(core.cljc:67)”
“medley.core$map_keys.invokeStatic(core.cljc:89)”
“medley.core$map_keys.invoke(core.cljc:86)”
“–> pulse.render.body$column_name.invokeStatic(body.clj:71)”
“pulse.render.body$column_name.invoke(body.clj:67)”
“pulse.render.body$query_results__GT_header_row$iter__32007__32011$fn__32012.invoke(body.clj:86)”
“pulse.render.table$render_table_head$iter__31855__31859$fn__31860.invoke(table.clj:59)”
“api.pulse$fn__63442.invokeStatic(pulse.clj:166)”
“api.pulse$fn__63442.invoke(pulse.clj:159)”
“middleware.auth$enforce_authentication$fn__66187.invoke(auth.clj:14)”
“routes$fn__67541$fn__67542.doInvoke(routes.clj:56)”
“middleware.exceptions$catch_uncaught_exceptions$fn__66286.invoke(exceptions.clj:97)”
“middleware.exceptions$catch_api_exceptions$fn__66283.invoke(exceptions.clj:85)”
“middleware.log$log_api_call$fn__67917$fn__67918.invoke(log.clj:178)”
“middleware.log$log_api_call$fn__67917.invoke(log.clj:172)”
“middleware.security$add_security_headers$fn__66249.invoke(security.clj:121)”
“middleware.json$wrap_json_body$fn__67622.invoke(json.clj:64)”
“middleware.json$wrap_streamed_json_response$fn__67640.invoke(json.clj:100)”
“middleware.misc$maybe_set_site_url$fn__67946.invoke(misc.clj:58)”
“middleware.session$bind_current_user$fn__62772$fn__62773.invoke(session.clj:209)”
“middleware.session$do_with_current_user.invokeStatic(session.clj:184)”
“middleware.session$do_with_current_user.invoke(session.clj:177)”
“middleware.session$bind_current_user$fn__62772.invoke(session.clj:208)”
“middleware.session$wrap_current_user_id$fn__62757.invoke(session.clj:161)”
“middleware.session$wrap_session_id$fn__62701.invoke(session.clj:125)”
“middleware.auth$wrap_api_key$fn__66195.invoke(auth.clj:27)”
“middleware.misc$bind_user_locale$fn__67949.invoke(misc.clj:74)”
“middleware.misc$add_content_type$fn__67932.invoke(misc.clj:29)”
“middleware.misc$disable_streaming_buffering$fn__67957.invoke(misc.clj:89)”)}

@flamber

diag info:

{
“browser-info”: {
“language”: “en-US”,
“platform”: “Win32”,
“userAgent”: “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.116 Safari/537.36”,
“vendor”: “Google Inc.”
},
“system-info”: {
“java.runtime.name”: “OpenJDK Runtime Environment”,
“java.runtime.version”: “1.8.0_242-b08”,
“java.vendor”: “Oracle Corporation”,
“java.vendor.url”: “http://java.oracle.com/”,
“java.version”: “1.8.0_242”,
“java.vm.name”: “OpenJDK 64-Bit Server VM”,
“java.vm.version”: “25.242-b08”,
“os.name”: “Linux”,
“os.version”: “3.10.0-1062.9.1.el7.x86_64”,
“user.language”: “en”,
“user.timezone”: “US/Central”
},
“metabase-info”: {
“databases”: [
“oracle”,
“sqlserver”
],
“hosting-env”: “unknown”,
“application-database”: “h2”,
“application-database-details”: {
“database”: {
“name”: “H2”,
“version”: “1.4.197 (2018-03-18)”
},
“jdbc-driver”: {
“name”: “H2 JDBC Driver”,
“version”: “1.4.197 (2018-03-18)”
}
},
“run-mode”: “prod”,
“version”: {
“tag”: “v0.34.2”,
“date”: “2020-02-04”,
“branch”: “release-0.34.x”,
“hash”: “dab738c”
},
“settings”: {
“report-timezone”: “US/Central”
}
}
}

@bpho Could it be that you’re seeing this issue about zero-date columns?
https://github.com/metabase/metabase/issues/11665
Since it’s a specific question that fails to load in pulse, then it sounds like that issue, but any additional information you can give would help.

@flamber Definitely sounds like it could be. Will try a suitable workaround in Oracle syntax. Any plans to address this in future update?

@flamber Workaround to populate the null date column is in place, however, doesn’t resolve this issue.

@bpho Can you give any other details about the question, like which the visualization, types of columns and such?
Can you always reproduce the issue or is it only specific tables that causes the question to fail on pulse?
I don’t have access to your data, so you’ll have to debug some more.

@flamber I was able to get around this by simply creating new versions of the ‘null-date-column’ amended questions, and creating a new Pulse.

For some reason, the existing amended questions persistently failed to load, despite having identical code.

@bpho Great that you found a workaround! So there was a null date column somewhere in the failing question? Any extra information will help us debug the issue much easier and try to find a fix.

@flamber The failing question had a SQL generated rollup, thus the null field in the date column.

1 Like