We're reclaiming inactive PDIs to keep them available for active builders. Learn what's changing, who's affected, and how to protect your work. Read More

scheduled Job failed due to error Did not get a response from the MID server after waiting for 305

vinitaraico
Tera Contributor

‎06-28-2024 02:28 AM

Hi All,

 

scheduled Job failed due to error Did not get a response from the MID server after waiting for 305

I found one Servicenow KA -

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0858700

 

According to the KB To prevent this issue from happening it is recommended to set Connect timeout and Query timeout values for all the JDBC data sources.

I wanted to know the steps to perform this Permanent solution from where we can set Connect timeout and query timeout

0 Helpfuls
  • 945 Views
2 REPLIES 2

Not applicable

‎06-28-2024 03:31 AM

Hi @vinitaraico 

Connection timeout and Query timeout fields are available on JDBC data source. Refer following documentation

https://docs.servicenow.com/bundle/tokyo-platform-administration/page/administer/import-sets/task/cr...

Thanks,

Swathi

vinitaraico
Tera Contributor

‎07-01-2024 10:34 AM

what is the recommended setting for query and connection timeout on data source

0 Helpfuls