Hi everyone 🖐️, I’m currently testing Elementary and I’m running into an issue when executing:

edr report

I get the following error:

{"info": {"name": "RunningOperationCaughtError", "code": "Q001", "msg": 
"Encountered an error while running operation: Database Error
('connection time out', TimeoutError(10060))"}}

From what I understand,

edr report

queries the Elementary tables stored in my data warehouse (Redshift). My Redshift cluster is deployed inside a private VPC, and I suspect the timeout happens because my current IP address is not allowed to access it. So my assumption is: • The error is network-related • I probably need to request access (IP whitelisting / VPN / bastion / security group update) Does that sound correct? Has anyone experienced this specific

TimeoutError(10060)

when running

edr report

? I also have another (beginner) question — sorry if it’s basic 🙂 Is it possible to generate one single EDR report that aggregates multiple dbt projects or multiple dbt jobs, and then filter inside the report afterward? For example: Several dbt jobs (or even separate dbt projects) All writing to the same Elementary schema • Then generate one global report with

edr report

• And filter by invocation / project / time range afterward Is this a recommended approach? How are people usually handling multi-project or multi-job reporting with Elementary? Thanks a lot in advance 🙏

Hey @Chaimae el hajoui! Are you still experiencing this error? I can take a deeper look. Your question makes a lot of sense 🙂 An Elementary schema and a report are per project. We actually have multi-project setup that was recently released on Elementary Cloud, feel free to learn about it here! So far I haven't encountered a good multi-project setup on Elementary OSS (we suggest unioning the Elementary schema tables, but I don't think anyone was successful yet). Let me know what you think!

Hey @Noya Offer Thank you very much for your response. To clarify my understanding: once the Elementary schemas are generated as part of the dbt run or dbt build process for each project, we would then need to consolidate the relevant tables using a UNION ALL to create a unified reporting layer for our BI tool. This consolidation step would therefore be handled on our side rather than automatically within Elementary. Additionally, my understanding is that this type of centralized view is only available in the Elementary Cloud version - could you please confirm?

Hey @Chaimae el hajoui, exactly 🙏