If flow designer was used prior to upgrade to Madrid an index may be missing on sys_flow_context.execution_id.  This missing index will cause performance issues with queries as the size of the number of flow executions grows.

Steps to Reproduce

1. Start with a London instance.
2. Define a flow and execute it several times to ensure there are multiple rows in the sys_flow_context table.
3. Upgrade the instance from London to Madrid.
4. Look at the indexes present on sys_flow_context and observe that there is no index on execution_id.

* The unique index could not be created due to the existing rows in sys_flow_context.  The issue will not occur on a instance with 0 or 1 rows in sys_flow_context (zbooted instances for example)


Manually create an index on sys_flow_context.execution_id.

Related Problem: PRB1420648

Seen In

There is no data to report.

Intended Fix Version


Fixed In

New York Patch 12
Orlando Patch 9
Paris Patch 3

Safe Harbor Statement

This "Intended Fix Version" information is meant to outline ServiceNow's general product direction and should not be relied upon in making a purchasing decision. The information provided here is for information purposes only and may not be incorporated into any contract. It is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remains at ServiceNow's sole discretion.

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2020-10-21 09:54:35