A loop repeating X times on a webservice call. Sometime, one of these calls stuck and stay "RUNNING" indefinitely.
Due to this:
- The next scheduled execution doesn't start because previous one is still running. Deleting corresponding line in the log database does not solve this as there is something still "running" at runtime level (no return code received).
- It's impossible to stop it through analytics (right click > "Stop" action).
For now, only solution is to restart the runtime (with a kill command). Also, it happen on different webservices after a variable number of iterations (sometimes 1, sometimes 50). (17.4.2 runtime / S19 Designer)
Best Answer
G
Gaurav Srivastava
said
over 2 years ago
We can solve this problem by migrating to version S20.0.5 of the designer & the runtime which bring many options/improvements to handle REST APIs particularly at the metadata level.
1) Add timeout at the metadata level:
2) An error tolerance as well as a number of "retries" in case of error:
1 Comment
G
Gaurav Srivastava
said
over 2 years ago
Answer
We can solve this problem by migrating to version S20.0.5 of the designer & the runtime which bring many options/improvements to handle REST APIs particularly at the metadata level.
1) Add timeout at the metadata level:
2) An error tolerance as well as a number of "retries" in case of error:
Gaurav Srivastava
A loop repeating X times on a webservice call. Sometime, one of these calls stuck and stay "RUNNING" indefinitely.
Due to this:
- The next scheduled execution doesn't start because previous one is still running. Deleting corresponding line in the log database does not solve this as there is something still "running" at runtime level (no return code received).
- It's impossible to stop it through analytics (right click > "Stop" action).
For now, only solution is to restart the runtime (with a kill command). Also, it happen on different webservices after a variable number of iterations (sometimes 1, sometimes 50). (17.4.2 runtime / S19 Designer)
We can solve this problem by migrating to version S20.0.5 of the designer & the runtime which bring many options/improvements to handle REST APIs particularly at the metadata level.
1) Add timeout at the metadata level:
2) An error tolerance as well as a number of "retries" in case of error:
Gaurav Srivastava
We can solve this problem by migrating to version S20.0.5 of the designer & the runtime which bring many options/improvements to handle REST APIs particularly at the metadata level.
1) Add timeout at the metadata level:
2) An error tolerance as well as a number of "retries" in case of error:
-
File external resolver with encrypted value
-
UNIQUE TEMP TABLE NAMES
-
Previous step name from a sub-process of execute delivery
-
Dropping multiple tables at once in XDI
-
Freeze Designer and corrupted workspace
-
FileWait/Move/Copy: FileInclude with space
-
Loop excel files
-
Change SVN user in the Designer
-
How to Specify the JVM used by the Designer?
See all 64 topics