Run Integration Action Bot: Simulation API Inconsistent Responses (200/500)

Q&A
1

Hi Team,
We have an integration bot in UESIO (3rd_eye/financial_planner/run_all) that triggers the 3rd Eyes Simulation API at the following endpoint:

POST https://stage.3rd-eyes.com/api/public/v1/simulations?scenarioSpace=default_2c

Functionality:

We are using the Run Integration Action Bot in UESIO, where the complete payload is passed in the params.

The bot sends a payload containing:

User age (age)

Investment strategy (strategy)

Pillar 1 & Pillar 2 incomes (piller1_income, piller2_income)

Pillar 3a current assets (piller3a_current_value)

Pillar 3a yearly contribution (yearly_contribution)

Other asset classes (Liquidity, Bonds, Shares)

Monthly retirement expenses (retire_monthly_expences)

The payload is dynamically built in the bot and is reused for:

Other Assets API Call (Assets: CS_EUR, EQ_W, BD_W)

Pillar 3a API Call (Assets based on selected strategy: Cash, Balanced, Equities)

Pension Age Simulation API Call (Combining strategy and advisory assets)

Issue:

While the API usually returns correct results, with the same payload we sometimes receive a 500 Internal Server Error and sometimes a successful 200 OK response. There are no changes made to the payload between these calls.

Expected Behavior:

The API should reliably process the payload and return a 200 OK response with simulation results.

Steps to Reproduce:

Trigger the bot with:

age: 45

retire_monthly_expences: 4000

piller1_income: 1200

piller2_income: 800

piller3a_current_value: 50000

yearly_contribution: 6826

strategy: Balanced

liquidity: 10000

bonds: 5000

shares: 15000

Observe that the same payload sometimes succeeds and sometimes returns a 500 error.

Additional Notes:

The same request payload can succeed or fail, indicating a possible server-side issue or resource limitation.

We are using X-API-Key authentication consistently; keys are valid.

Attached below is a screenshot of the error, which appears randomly when the bot is triggered.

image
image1434×809 79.1 KB

image
image1439×797 64.1 KB

2

Hello @rbdwt09 -

The reason you are seeing the intermittent failure is due to the length of time that the bot is taking to complete. By default, a bot has 5 seconds to complete although you can configure this to a max of 45 seconds via the timeout property in the bot.yaml.

name: mylistner
public: true
type: LISTENER
dialect: TYPESCRIPT
timeout: 15
3

yes that worked we can close this issue.