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)â)}
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.