Hello @Helga Afonso ,

Please check the Service Center logs for any errors, you can see how to do that here:

https://success.outsystems.com/support/troubleshooting/getting_logs_for_troubleshooting_purposes/service_center_logs/

@Helga Afonso ,

have you added any filters or can can you check aggerates have record or not.

and you are using timer so have schedule it or trigger when publish?

Can you share oml?

Hello.

There are many things you can be doing wrong, but a breakpoint will tell which one.

Are you running the timer?

Is that aggregate returning something?

How are you checking if Create worked?

Do you reach the end?

In terms of best practices, there are hour long videos you can watch, but here I'd say you need a Commit inside the loop after create, just to make sure what you created is saved.

@Helga Afonso , please share a screenshot of the properties of the Assign and CreateRequest Nodes.

btw you could attach a breakpoint and debug as suggested by @Nuno Reis.

Hi @Helga Afonso ,

Can you please debug your logic to find the cause of the issue? Check this file for  Debugging,

To debug the timer issue, follow these steps:

1. Add a breakpoint at the Start node.
2. Set the module to 'This Module' and begin the debugging process.
3. Trigger the timer through the service center.

Hi,
1.Add a debug log inside the CreateRequest action 
2.Check If Consultants List is Empty 
3.Double-check the implementation of Create Request. Ensure that the necessary fields are being set correctly.
4.If Create Request requires mandatory fields that are missing, the request might not be inserted.
5.Verify Filters in GetRequests 
6.If you're running a background timer, sometimes newly inserted records may not appear immediately due to caching. Try refreshing the database manually. 

Thanks,
Sahana

Hi Helga Afonso ,

Please first check if the aggregate returning values if you use any filters using debugging method and check if the length of an attribute in DB for each is exceeded by the value you try to assign to it, because OutSystems will not allow you to push the data, generating an error message indicating that the value is too long for the specified attribute length; essentially preventing you from saving data that surpasses the defined limits. 

Key points to remember:

Attribute length definition:When creating an attribute in OutSystems, you specify a "Length" property which defines the maximum character count allowed for that attribute. 

Error on exceeding length:If you attempt to enter a value longer than the defined attribute length, OutSystems will throw an error during data submission, preventing the data from being saved. 

Hope it helps you to find solution.

Thanks,

Anjana Devi J B

it is hard to tell with such a small information. Please try to debug the flow.

If possible please share oml or create a small dummy application and check it.