Loading...
Loading...
After upgrade to Washington (Patch 3 and under), Orchestration workflows with a JDBC activity will fail to authenticate due to a credentials issue with JDBCOrchestrationProbe This only affects JDBC activities from the old workflow product. It does not affect Flow Designer JDBC step or Data source JDBC integrations.
Make sure instance is on Washington (under patch 4) Navigate to IntegrationHub > Connections Create a JDBC Connection for a database Open Workflow Editor and click on the Custom tab Click the Plus icon and select JDBC Configure step to use the connection and credential created in step 2 Click test inputs Expected: call succeeds and data is returned. Actual: call fails with authentication error
There is no workaround available for this issue. Please upgrade to a fixed version when available (Washington Patch 4+, Washington DC Patch 3 Hotfix 1). FAQ Q: What can I do if my instance is experiencing this issue? A: Unfortunately, there are no workarounds. Please upgrade to a fixed version listed above, when it becomes available. Q: How can I tell if my instance is affected by this issue? A: You must be on Washington (pre Patch 4). You can follow the steps to reproduce above to test. This only affects JDBC activities from the old workflow product. It does not affect Flow Designer JDBC step or Data source JDBC integrations. Q: Can this issue affect an on-premise instance? A: Yes
PRB1760522
Click on a version to see all relevant bugs
ServiceNow Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.